CryptPad Outage History
CryptPad is up right nowPingoru has recorded 10 incidents for CryptPad: 6 in the last 12 months and 1 in the last 90 days.
Incidents, newest first
Minor August 25, 2026 Planned maintenance 1d 22h
Started Aug 25, 2026, 10:00 AM UTC· resolved Aug 27, 2026, 08:29 AM UTC
- investigating Aug 25, 2026, 10:00 AM UTC
CryptPad.fr will be unavailable for a few minutes starting at 9AM CEST on Thursday 27th August.
Minor May 20, 2026 Ongoing maintenance 3h 1m
Started May 20, 2026, 01:27 PM UTC· resolved May 20, 2026, 04:29 PM UTC
- investigating May 20, 2026, 01:27 PM UTC
We are upgrading a number of machines that host CryptPad-adjacent services (forum, translations, etc). These may be unavailable
Minor May 20, 2026 CryptPad.fr - Issues with Office documents 7h 25m
Started May 20, 2026, 09:03 AM UTC· resolved May 20, 2026, 04:28 PM UTC
- investigating May 20, 2026, 09:03 AM UTC
We are currently getting reports of office documents failing to open on cryptpad.fr please bear with us as we work to resolve this issue.
Minor May 19, 2026 Planned maintenance on 20th May between 9AM and 11AM CEST 22h 23m
Started May 19, 2026, 10:40 AM UTC· resolved May 20, 2026, 09:03 AM UTC
- investigating May 19, 2026, 10:40 AM UTC
We will be carrying some upgrades on our infrastructure. The service may be disrupted or unavailable during that time. Our team will do their best to keep disruption to a minimum.
Minor March 2, 2026 Ongoing server upgrade 7d 19h
Started Mar 02, 2026, 03:35 PM UTC· resolved Mar 10, 2026, 11:00 AM UTC
- investigating Mar 02, 2026, 03:35 PM UTC
Update - March 5th 🚧 We are still working on resolving some issues linked to yesterday's deployment on cryptpad.fr. The service may be disrupted today as our team attempts to diagnose and solve problems. Thank you for bearing with us. **Planned maintenance - Wednesday March 4th starting at 9AM CET** 🏡 🚧 📢 PSA: We are planning some major maintenance work on our flagship instance cryptpad.fr this Wednesday March 4th starting at 9AM CET. Users may experience the service being interrupted, slow, or unresponsive. Unfortunately cryptpad.fr users are already familiar with this experience on an almost daily basis recently due to high usage that stretches our existing architecture beyond capacity. We will be deploying our new scalable server, completely re-built to resolve these issues. There may be disruptions due to this deployment. We have been testing this code for weeks but we may have adjustments to make as it meets the real world, this could require us to restart the service multiple times. We will do our very best to minimize disruptions, and hope that this will pave the way to a much smoother experience for everyone on cryptpad.fr
Minor January 28, 2026 Ongoing technical issue on cryptpad.fr –
Started Jan 28, 2026, 07:53 PM UTC· resolved Jan 28, 2026, 07:53 PM UTC
- investigating Jan 28, 2026, 07:53 PM UTC
🚧 Cryptpad.fr is currently operating a "degraded" service to reduce the impact of ongoing technical issues. Users can open and modify existing documents, but not add new things to their drive. We hope to resume regular service as soon as possible
Minor September 25, 2025 Weblate maintenance –
Started Sep 25, 2025, 08:05 AM UTC· resolved Sep 25, 2025, 08:05 AM UTC
- investigating Sep 25, 2025, 08:05 AM UTC
Multiple maintenance tasks are being performed today (2025-09-25) on our [Weblate instance](https://weblate.cryptpad.org). It may generate some unavailability. Thank you for your understanding.
Minor September 8, 2025 Performances issues –
Started Sep 08, 2025, 07:46 AM UTC· resolved Sep 08, 2025, 07:46 AM UTC
- investigating Sep 08, 2025, 07:46 AM UTC
Our CryptPad.fr flagship instance is facing performances issues. We are monitoring the service closely, thanks for your patience.
Minor February 18, 2025 CryptPad.fr performances degradation 15h 1m
Started Feb 18, 2025, 04:59 PM UTC· resolved Feb 19, 2025, 08:00 AM UTC
- investigating Feb 18, 2025, 04:59 PM UTC
We fixed an issue where our flagship instance performances would degrade and forbid you to create or open documents. It was due to a mixture of lack of available virtual memory and reaching the limits of open files on Nginx. Everything is back to normal now. Thanks for your patience and sorry for the annoyance.