Störungsverlauf von Readme

1. 23. Oktober 2026 um 15:46 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das beim Laden von Dokumentationsseiten erhöhte 503-Fehler und Timeouts verursacht.

2. 23. Oktober 2026 um 15:46 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 23. Oktober 2026 um 15:47 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

4. 23. Oktober 2026 um 16:07 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

5. 23. Oktober 2026 um 16:09 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. Oktober 2026 um 22:44 UTCinvestigating

   Wir untersuchen derzeit, warum Seiten 404 zeigen

2. 14. Oktober 2026 um 22:51 UTCidentified

   Wir haben das Problem erkannt und arbeiten an einem Fix

3. 14. Oktober 2026 um 22:52 UTCmonitoring

   Der Fix wurde bereitgestellt und wir stellen derzeit die operativen Server bereit. Es kann einige zwischengespeicherte 404s geben, also lassen Sie den Support bitte wissen, wenn Sie immer noch Probleme haben

4. 14. Oktober 2026 um 22:55 UTCresolved

   Projekte sollten sich wieder zeigen. Bitte kontaktieren Sie [email protected], wenn Sie immer noch auf 404-Fehler stoßen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. September 2026 um 14:22 UTCinvestigating

   Wir untersuchen derzeit erhöhte Latenz und langsame Reaktionszeiten, die Hubs betreffen. Aktiv arbeiten, um die Ursache zu identifizieren und den normalen Service wiederherzustellen.

2. 22. September 2026 um 14:41 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen derzeit die Ergebnisse. Die Leistung sollte sich wieder normalisieren.

3. 22. September 2026 um 15:03 UTCmonitoring

   Wir haben zusätzliche Faktoren identifiziert und arbeiten aktiv daran, sie zu beheben.

4. 22. September 2026 um 15:16 UTCmonitoring

   Wir werden weiterhin auf weitere Probleme achten.

5. 22. September 2026 um 16:44 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 8. September 2026 um 16:04 UTCinvestigating

   Unsere Admin-Schnittstelle erlebt einen Ausfall. Die Fähigkeit von Endbenutzern, Ihren ReadMe-Entwickler-Hub zu besuchen, ist nicht betroffen.

2. 8. September 2026 um 16:15 UTCinvestigating

   Wir konnten die Situation lösen. Es kann einige intermittierende Trägheit für die nächsten Minuten sein.

3. 8. September 2026 um 16:16 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 21. August 2026 um 16:36 UTCidentified

   Wir erleben derzeit langsame Suchergebnisse in Kunden-Hubs

2. 21. August 2026 um 18:21 UTCresolved

   Wir haben die Suche neu indexiert und die Leistung hat sich verbessert. Bitte E-Mail [email protected], wenn Sie immer noch Probleme mit der Suche sehen

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 24. Juli 2026 um 12:22 UTCmonitoring

   Degradierte Leistung aufgrund von Infrastrukturproblemen von Drittanbietern. Wir beobachten diese Situation und arbeiten daran, die Stabilität auf unserer Seite zu erhalten.

2. 24. Juli 2026 um 13:37 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 17. Juni 2026 um 15:28 UTCinvestigating

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

2. 17. Juni 2026 um 18:10 UTCresolved

   This incident was resolved and normal site function has been resolved

1. 28. Mai 2026 um 13:40 UTCinvestigating

   We're actively investigating this issue.

2. 28. Mai 2026 um 13:43 UTCidentified

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

3. 28. Mai 2026 um 14:35 UTCidentified

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

4. 28. Mai 2026 um 15:27 UTCmonitoring

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

5. 28. Mai 2026 um 15:33 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 28. Mai 2026 um 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 um 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 um 01:49 UTCmonitoring

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

9. 29. Mai 2026 um 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 um 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. Juni 2026 um 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 um 13:51 UTCinvestigating

   We are currently investigating this issue.

2. 27. Mai 2026 um 14:52 UTCidentified

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

3. 27. Mai 2026 um 15:57 UTCmonitoring

   We're slowly recovering and monitoring the situation.

4. 27. Mai 2026 um 17:08 UTCmonitoring

   We are monitoring the issue.

5. 27. Mai 2026 um 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 um 17:43 UTCinvestigating

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

7. 27. Mai 2026 um 17:47 UTCinvestigating

   We are continuing to investigate this issue.

8. 27. Mai 2026 um 18:02 UTCmonitoring

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

9. 27. Mai 2026 um 20:54 UTCmonitoring

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

10. 27. Mai 2026 um 22:37 UTCresolved

    This incident has been resolved.

11. 3. Juni 2026 um 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 um 17:41 UTCinvestigating

   We are experiencing slow performance across customer hubs

2. 26. Mai 2026 um 17:49 UTCmonitoring

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

3. 27. Mai 2026 um 03:54 UTCresolved

   This incident has been resolved.

1. 26. Mai 2026 um 13:39 UTCinvestigating

   We are currently investigating this issue.

2. 26. Mai 2026 um 14:26 UTCmonitoring

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

3. 26. Mai 2026 um 15:37 UTCresolved

   This incident has been resolved.

1. 12. Mai 2026 um 14:15 UTCidentified

   We are investigating slowness across hubs.

2. 12. Mai 2026 um 19:38 UTCmonitoring

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

3. 12. Mai 2026 um 21:10 UTCresolved

   This incident has been resolved.

1. 11. Mai 2026 um 15:43 UTCinvestigating

   We are currently investigating this issue.

2. 11. Mai 2026 um 16:03 UTCidentified

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

3. 11. Mai 2026 um 17:08 UTCmonitoring

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

4. 11. Mai 2026 um 18:34 UTCresolved

   This incident has been resolved.

1. 7. Mai 2026 um 23:43 UTCinvestigating

   We are currently investigating an issue creating changelogs

2. 8. Mai 2026 um 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 um 03:02 UTCmonitoring

   We have deployed the fix and are monitoring the results

4. 8. Mai 2026 um 03:18 UTCresolved

   This incident has been resolved.

1. 28. April 2026 um 18:38 UTCinvestigating

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

2. 28. April 2026 um 19:02 UTCidentified

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

3. 28. April 2026 um 19:31 UTCresolved

   Branches and versions can now be created successfully

1. 24. April 2026 um 12:17 UTCinvestigating

   We are currently investigating this issue.

2. 24. April 2026 um 12:29 UTCinvestigating

   We are continuing to investigate this issue.

3. 24. April 2026 um 13:42 UTCmonitoring

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

4. 24. April 2026 um 15:11 UTCresolved

   This incident has been resolved.

1. 22. April 2026 um 14:35 UTCinvestigating

   We are currently investigating downtime impacting admin users.

2. 22. April 2026 um 14:40 UTCidentified

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

3. 22. April 2026 um 14:53 UTCmonitoring

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

4. 22. April 2026 um 14:56 UTCmonitoring

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

5. 22. April 2026 um 14:59 UTCmonitoring

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

6. 22. April 2026 um 16:36 UTCresolved

   Issues with admin requests have been resolved.

1. 22. April 2026 um 02:59 UTCinvestigating

   We are currently investigating performance issues across the platform.

2. 22. April 2026 um 03:08 UTCidentified

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

3. 22. April 2026 um 03:43 UTCresolved

   Fix has been implemented and performance has stabilized.

1. 20. April 2026 um 20:05 UTCidentified

   The admin interface is experiencing slower than expected response times.

2. 20. April 2026 um 21:16 UTCmonitoring

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

3. 20. April 2026 um 21:20 UTCresolved

   This incident has been resolved.

1. 16. April 2026 um 16:07 UTCinvestigating

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

2. 16. April 2026 um 16:57 UTCmonitoring

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

3. 16. April 2026 um 19:25 UTCresolved

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