Historique des pannes de Readme

1. 23 octobre 2026 à 15:46 UTCinvestigating

   Nous enquêtons actuellement sur un problème causant des erreurs et des délais élevés de 503 lors du chargement des pages de documentation.

2. 23 octobre 2026 à 15:46 UTCinvestigating

   Nous continuons d'enquêter sur cette question.

3. 23 octobre 2026 à 15:47 UTCidentified

   Le problème a été identifié et une solution est en cours de mise en oeuvre.

4. 23 octobre 2026 à 16:07 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

5. 23 octobre 2026 à 16:09 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 14 octobre 2026 à 22:44 UTCinvestigating

   Nous cherchons actuellement pourquoi les pages montrent 404

2. 14 octobre 2026 à 22:51 UTCidentified

   Nous avons identifié le problème et nous travaillons sur une solution

3. 14 octobre 2026 à 22:52 UTCmonitoring

   La correction a été déployée et nous déployons actuellement les serveurs opérationnels. Il peut y avoir des caches 404s, alors s'il vous plaît faites savoir au support si vous êtes toujours en train de rencontrer des problèmes

4. 14 octobre 2026 à 22:55 UTCresolved

   Les projets devraient être présentés à nouveau. Veuillez contacter [email protected] si vous rencontrez toujours des erreurs 404.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 22 septembre 2026 à 14:22 UTCinvestigating

   Nous enquêtons actuellement sur une latence élevée et des temps de réponse lents affectant les centres. Travailler activement pour identifier la cause fondamentale et restaurer le service normal.

2. 22 septembre 2026 à 14:41 UTCmonitoring

   Un correctif a été mis en place et nous suivons actuellement les résultats. La performance devrait revenir à la normale.

3. 22 septembre 2026 à 15:03 UTCmonitoring

   Nous avons identifié d'autres facteurs contributifs et nous travaillons activement à les corriger.

4. 22 septembre 2026 à 15:16 UTCmonitoring

   Nous restons à l'affût de tout autre problème.

5. 22 septembre 2026 à 16:44 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 8 septembre 2026 à 16:04 UTCinvestigating

   Notre interface Admin connaît une panne. La capacité des utilisateurs finaux de visiter votre hub développeur ReadMe n'est pas affectée.

2. 8 septembre 2026 à 16:15 UTCinvestigating

   Nous avons pu résoudre la situation. Il peut y avoir une certaine paresse intermittente pendant les prochaines minutes.

3. 8 septembre 2026 à 16:16 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 21 août 2026 à 16:36 UTCidentified

   Nous connaissons actuellement des résultats de recherche lents dans les centres clients

2. 21 août 2026 à 18:21 UTCresolved

   Nous avons réindexé la recherche et la performance s'est améliorée. S'il vous plaît e-mail [email protected] si vous voyez toujours des problèmes avec la recherche

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 24 juillet 2026 à 12:22 UTCmonitoring

   Résultats obtenus en raison de problèmes d'infrastructure de tiers. Nous suivons cette situation et nous travaillons à maintenir la stabilité à notre fin.

2. 24 juillet 2026 à 13:37 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 17 juin 2026 à 15:28 UTCinvestigating

   We are currently investigating an incident related to API Reference pages.

2. 17 juin 2026 à 18:10 UTCresolved

   This incident was resolved and normal site function has been resolved

1. 28 mai 2026 à 13:40 UTCinvestigating

   We're actively investigating this issue.

2. 28 mai 2026 à 13:43 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 28 mai 2026 à 14:35 UTCidentified

   Systems are getting back up. We're continuing to work on a permanent fix for this issue.

4. 28 mai 2026 à 15:27 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 28 mai 2026 à 15:33 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 28 mai 2026 à 17:53 UTCmonitoring

   We are receiving reports of degraded performance and are actively investigating. We will provide updates as more information becomes available.

7. 28 mai 2026 à 20:04 UTCmonitoring

   Systems appear stable and we are actively rolling out a series of fixes. We will continue to monitor and provide updates

8. 29 mai 2026 à 01:49 UTCmonitoring

   Systems remain stable. Improvements and fixes have been rolled out and we are continuing to monitor.

9. 29 mai 2026 à 17:03 UTCmonitoring

   Systems remain stable, and we are continuing to monitor the situation. Bi-directional sync was on a maintenance job from 9:50 - 11:59 AM (ET) and is now operational.

10. 29 mai 2026 à 18:36 UTCmonitoring

    Systems remain stable and our team continues to deploy targeted fixes. Work is ongoing to address degraded read performance across the system, including serving all 404s from cache. We’ll be actively monitoring over the weekend, and we will provide a full RCA next week.

11. 1 juin 2026 à 18:16 UTCresolved

    Our systems have been stable since Friday, May 29th. We're monitoring closely and improving spike detection to prevent recurrence and adding proactive capacity monitoring to detect admin dashboard degradation before it impacts customers. Full root cause analysis coming soon. Thanks for your patience and understanding.

1. 27 mai 2026 à 13:51 UTCinvestigating

   We are currently investigating this issue.

2. 27 mai 2026 à 14:52 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 27 mai 2026 à 15:57 UTCmonitoring

   We're slowly recovering and monitoring the situation.

4. 27 mai 2026 à 17:08 UTCmonitoring

   We are monitoring the issue.

5. 27 mai 2026 à 17:17 UTCmonitoring

   Updated 6/3: A routine configuration update coincided with the downtime window, which led us to initially identify it as the cause. Further investigation confirmed the two were unrelated. See the postmortem for full details.

6. 27 mai 2026 à 17:43 UTCinvestigating

   We are seeing some slow performance, possibly 500 errors. investigating

7. 27 mai 2026 à 17:47 UTCinvestigating

   We are continuing to investigate this issue.

8. 27 mai 2026 à 18:02 UTCmonitoring

   Performance has improved, but we're still investigating the issue.

9. 27 mai 2026 à 20:54 UTCmonitoring

   Performance and loading is still being affected, and we're in the process of rolling out fixes

10. 27 mai 2026 à 22:37 UTCresolved

    This incident has been resolved.

11. 3 juin 2026 à 15:28 UTCpostmortem

    ### What Happened Beginning Tuesday, May 26, 2026, customers were experiencing slow loading and 503 errors across ReadMe-hosted docs and the admin dashboard. The outage was intermittent but recurring, with the worst periods hitting during business hours when traffic spiked. ### Root Cause An internal data backup process was generating excessive I/O on our storage layer. Under normal traffic conditions, this additional load was manageable. But when it coincided with peak customer traffic and elevated bot activity, total I/O demand exceeded system capacity, causing cascading request timeouts. The maintenance process ran on a recurring schedule, which is why the degradation followed a predictable pattern of spikes throughout each day. Separately, a surge in bot traffic to non-existent pages \(404s\) amplified the problem because those requests were not being served from cache. ### Resolution **Immediate fix:** We identified and disabled the maintenance process causing the excess I/O load. Within three hours, storage utilization returned to normal levels and remained stable. **Additional improvements shipped during the incident:** * Expanded caching across multiple layers, significantly reducing load on backend storage * Hardened 404 handling to serve error pages from cache instead of hitting the backend * Implemented rate limiting and IP-based protections against abusive bot traffic * Optimized several high-traffic API endpoints to reduce redundant backend calls * Added new monitoring and alerting for storage I/O thresholds ### Timeline May 26 - June 1, 2026 | Time | Status | Details | | --- | --- | --- | | Mon 5/26, 6:39 AM PDT | Investigating | Issue reported | | Mon 5/26, 7:26 AM PDT | Monitoring | Fix implemented, monitoring results | | Mon 5/26, 8:37 AM PDT | Resolved | Admin hub incident resolved | | Mon 5/26, 10:41 AM PDT | Investigating | Slow performance across customer hubs | | Mon 5/26, 10:49 AM PDT | Monitoring | Quick fix applied, investigating thorough fix | | Mon 5/26, 8:54 PM PDT | Resolved | Customer hub incident resolved | | Tue 5/27, 6:51 AM PDT | Investigating | Issue reported | | Tue 5/27, 7:52 AM PDT | Identified | Fix in progress | | Tue 5/27, 8:57 AM PDT | Monitoring | Slowly recovering | | Tue 5/27, 10:17 AM PDT | Update | Updated 6/3: A routine configuration update coincided with the downtime window, which led us to initially identify it as the cause. Further investigation confirmed the two were unrelated. See root cause and resolution above. | | Tue 5/27, 1:54 PM PDT | Update | Performance and loading still affected, rolling out fixes | | Tue 5/27, 3:37 PM PDT | Resolved | Incident resolved | | Wed 5/28, 6:40 AM PDT | Investigating | Issue reported | | Wed 5/28, 6:43 AM PDT | Identified | Fix being implemented | | Wed 5/28, 7:35 AM PDT | Update | Systems coming back up, working on permanent fix | | Wed 5/28, 8:27 AM PDT | Monitoring | Fix implemented, monitoring results | | Wed 5/28, 10:53 AM PDT | Update | Reports of degraded performance, actively investigating | | Wed 5/28, 1:04 PM PDT | Update | Systems appear stable, rolling out fixes | | Wed 5/28, 6:49 PM PDT | Monitoring | Improvements and fixes deployed, continuing to monitor | | Thu 5/29, 10:03 AM PDT | Monitoring | Systems stable. Bi-directional sync maintenance 9:50–11:59 AM ET. | | Thu 5/29, 11:36 AM PDT | Monitoring | Deploying targeted fixes. Serving all 404s from cache. Degraded read performance. | | Fri 5/30 | Monitoring | Monitoring continues | | Sat 5/31 | Monitoring | Weekend monitoring | | Mon 6/1, 11:16 AM PDT | Resolved | Root cause identified and resolved. Systems stable since Thursday, May 29. | ### Path Forward We are using this incident to make lasting improvements to reliability and incident response: * **Storage capacity and isolation:** Restructuring how background processes interact with production storage to eliminate contention under load. * **Caching and performance:** The caching improvements shipped during the incident are permanent. We are continuing to expand cache coverage across additional endpoints and page types. * **Bot and traffic protection:** Strengthening rate limiting and abuse detection to prevent bot traffic from contributing to backend load. * **Monitoring and alerting:** Adding proactive capacity monitoring with earlier thresholds so the team can intervene before customers are affected. * **Incident response:** Improving our internal processes for faster escalation and more frequent status page updates during multi-day incidents. ### Final Note During the incident, we posted an update referencing a platform update. That was our initial hypothesis based on timing. Further investigation confirmed it was unrelated. The change in question was a routine, isolated configuration update and had no impact on the outage or any other customers. We should have waited for confirmation before publishing it, and we're tightening our internal process for status page updates as a result. We know how critical your documentation is to your customers, and this level of disruption is not acceptable. We have already shipped meaningful improvements to prevent recurrence, and the work outlined above will continue through the coming weeks. If you have questions, reach out to your account team or contact [[email protected]](mailto:[email protected]).

1. 26 mai 2026 à 17:41 UTCinvestigating

   We are experiencing slow performance across customer hubs

2. 26 mai 2026 à 17:49 UTCmonitoring

   We have identified and quickly fixed the issue and are currently investigating a more thorough fix

3. 27 mai 2026 à 03:54 UTCresolved

   This incident has been resolved.

1. 26 mai 2026 à 13:39 UTCinvestigating

   We are currently investigating this issue.

2. 26 mai 2026 à 14:26 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 26 mai 2026 à 15:37 UTCresolved

   This incident has been resolved.

1. 12 mai 2026 à 14:15 UTCidentified

   We are investigating slowness across hubs.

2. 12 mai 2026 à 19:38 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 12 mai 2026 à 21:10 UTCresolved

   This incident has been resolved.

1. 11 mai 2026 à 15:43 UTCinvestigating

   We are currently investigating this issue.

2. 11 mai 2026 à 16:03 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 11 mai 2026 à 17:08 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 11 mai 2026 à 18:34 UTCresolved

   This incident has been resolved.

1. 7 mai 2026 à 23:43 UTCinvestigating

   We are currently investigating an issue creating changelogs

2. 8 mai 2026 à 00:40 UTCidentified

   We have identified the issue preventing the changelog creation page from rendering correctly, and we are working on a fix

3. 8 mai 2026 à 03:02 UTCmonitoring

   We have deployed the fix and are monitoring the results

4. 8 mai 2026 à 03:18 UTCresolved

   This incident has been resolved.

1. 28 avril 2026 à 18:38 UTCinvestigating

   We are currently investigating an issue where customers are unable to create branches

2. 28 avril 2026 à 19:02 UTCidentified

   We have identified the issue and are currently looking into a fix

3. 28 avril 2026 à 19:31 UTCresolved

   Branches and versions can now be created successfully

1. 24 avril 2026 à 12:17 UTCinvestigating

   We are currently investigating this issue.

2. 24 avril 2026 à 12:29 UTCinvestigating

   We are continuing to investigate this issue.

3. 24 avril 2026 à 13:42 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 24 avril 2026 à 15:11 UTCresolved

   This incident has been resolved.

1. 22 avril 2026 à 14:35 UTCinvestigating

   We are currently investigating downtime impacting admin users.

2. 22 avril 2026 à 14:40 UTCidentified

   An issue has been identified with a third-party provider. A fix is being implemented.

3. 22 avril 2026 à 14:53 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 22 avril 2026 à 14:56 UTCmonitoring

   Admin dashboard is recovering and we are continuing to monitor for further issues.

5. 22 avril 2026 à 14:59 UTCmonitoring

   Fix has been applied and admin requests have recovered. We are continuing to monitor for any further issues.

6. 22 avril 2026 à 16:36 UTCresolved

   Issues with admin requests have been resolved.

1. 22 avril 2026 à 02:59 UTCinvestigating

   We are currently investigating performance issues across the platform.

2. 22 avril 2026 à 03:08 UTCidentified

   We've discovered the issue and have implemented a quick fix

3. 22 avril 2026 à 03:43 UTCresolved

   Fix has been implemented and performance has stabilized.

1. 20 avril 2026 à 20:05 UTCidentified

   The admin interface is experiencing slower than expected response times.

2. 20 avril 2026 à 21:16 UTCmonitoring

   Performance has returned to normal, and we are continuing to monitor.

3. 20 avril 2026 à 21:20 UTCresolved

   This incident has been resolved.

1. 16 avril 2026 à 16:07 UTCinvestigating

   We are getting reports of slow performance and 500 errors when loading pages

2. 16 avril 2026 à 16:57 UTCmonitoring

   We've stabilized our platform and our response times have improved. We are currently monitoring the situation.

3. 16 avril 2026 à 19:25 UTCresolved

   Performance has stabilized and we are no longer returning errors upon loading pages.