Readme Outage History

Readme is up right now

Pingoru has recorded 52 incidents for Readme: 28 in the last 12 months and 4 in the last 90 days.

Source: readmestatus.com

52incidents recorded
28last 12 months
4last 90 days
6 hourstypical duration
Incidents per month
0510AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Readme in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026921 of 720 (3%)
May 20267117 of 744 (16%)
June 2026121 of 720 (3%)
July 202611 of 744 (0%)
August 202612 of 744 (0%)
September 202623 of 720 (0%)
October 202610 of 520 (0%)

Incidents, newest first

Critical October 14, 2026 Projects are not loading 11m ReadMe Hubs, ReadMe Knowledge Base, Admin Dashboard, Developer Metrics

Started Oct 14, 2026, 10:44 PM UTC· resolved Oct 14, 2026, 10:55 PM UTC

  1. investigating Oct 14, 2026, 10:44 PM UTC

    We are currently investigating why pages are showing 404

  2. identified Oct 14, 2026, 10:51 PM UTC

    We have identified the issue and are working on a fix

  3. monitoring Oct 14, 2026, 10:52 PM UTC

    The fix has been deployed and we're currently deploying the operational servers. There may be some cached 404s, so please let support know if you are still running into issues

  4. resolved Oct 14, 2026, 10:55 PM UTC

    Projects should be showing again. Please contact [email protected] if you are still running into any 404 errors.

Read the full incident report →

Minor September 22, 2026 Degraded Performance Across Hubs 2h 21m ReadMe Hubs, ReadMe Knowledge Base, Admin Dashboard

Started Sep 22, 2026, 02:22 PM UTC· resolved Sep 22, 2026, 04:44 PM UTC

  1. investigating Sep 22, 2026, 02:22 PM UTC

    We're currently investigating elevated latency and slow response times affecting hubs. Actively working to identify the root cause and restore normal service.

  2. monitoring Sep 22, 2026, 02:41 PM UTC

    A fix has been implemented and we're currently monitoring the results. Performance should be returning to normal.

  3. monitoring Sep 22, 2026, 03:03 PM UTC

    We've identified additional contributing factors and are actively working to fix them.

  4. monitoring Sep 22, 2026, 03:16 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Sep 22, 2026, 04:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 8, 2026 Admin interface outage 11m Admin Dashboard

Started Sep 08, 2026, 04:04 PM UTC· resolved Sep 08, 2026, 04:16 PM UTC

  1. investigating Sep 08, 2026, 04:04 PM UTC

    Our Admin interface is experiencing an outage. The ability of end-users to visit your ReadMe developer hub is unaffected.

  2. investigating Sep 08, 2026, 04:15 PM UTC

    We were able to resolve the situation. There may be some intermittent sluggishness for the next few minutes.

  3. resolved Sep 08, 2026, 04:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 21, 2026 Slow search within customer hubs 1h 45m ReadMe Hubs

Started Aug 21, 2026, 04:36 PM UTC· resolved Aug 21, 2026, 06:21 PM UTC

  1. identified Aug 21, 2026, 04:36 PM UTC

    We are currently experiencing slow search results across customer hubs

  2. resolved Aug 21, 2026, 06:21 PM UTC

    We have re-indexed the search and performance has improved. Please e-mail [email protected] if you're still seeing issues with search

Read the full incident report →

Minor July 24, 2026 Degraded performance due to third-party infrastructure issues 1h 15m ReadMe Hubs, Admin Dashboard

Started Jul 24, 2026, 12:22 PM UTC· resolved Jul 24, 2026, 01:37 PM UTC

  1. monitoring Jul 24, 2026, 12:22 PM UTC

    Experiencing degraded performance due to third-party infrastructure issues. We are monitoring this situation and working to maintain stability on our end.

  2. resolved Jul 24, 2026, 01:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 17, 2026 API Reference Degradation 2h 41m

Started Jun 17, 2026, 03:28 PM UTC· resolved Jun 17, 2026, 06:10 PM UTC

  1. investigating Jun 17, 2026, 03:28 PM UTC

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

  2. resolved Jun 17, 2026, 06:10 PM UTC

    This incident was resolved and normal site function has been resolved

Read the full incident report →

Major May 28, 2026 Refactored Hubs Down 4d 4h ReadMe Hubs, ReadMe Knowledge Base, Admin Dashboard

Started May 28, 2026, 01:40 PM UTC· resolved Jun 01, 2026, 06:16 PM UTC

  1. investigating May 28, 2026, 01:40 PM UTC

    We're actively investigating this issue.

  2. identified May 28, 2026, 01:43 PM UTC

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

  3. identified May 28, 2026, 02:35 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring May 28, 2026, 03:27 PM UTC

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

  5. monitoring May 28, 2026, 03:33 PM UTC

    We are continuing to monitor for any further issues.

  6. monitoring May 28, 2026, 05:53 PM UTC

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

  7. monitoring May 28, 2026, 08:04 PM UTC

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

  8. monitoring May 29, 2026, 01:49 AM UTC

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

  9. monitoring May 29, 2026, 05:03 PM UTC

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

  10. monitoring May 29, 2026, 06:36 PM UTC

    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. resolved Jun 01, 2026, 06:16 PM UTC

    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.

Read the full incident report →

Critical May 27, 2026 ReadMe Refactored Outage 8h 46m ReadMe Hubs, ReadMe Knowledge Base, Admin Dashboard

Started May 27, 2026, 01:51 PM UTC· resolved May 27, 2026, 10:37 PM UTC

  1. investigating May 27, 2026, 01:51 PM UTC

    We are currently investigating this issue.

  2. identified May 27, 2026, 02:52 PM UTC

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

  3. monitoring May 27, 2026, 03:57 PM UTC

    We're slowly recovering and monitoring the situation.

  4. monitoring May 27, 2026, 05:08 PM UTC

    We migrated a large customer to our new platform which caused temporary read/write disruptions. We have halted all migrations while we investigate and implement safeguards to prevent recurrence.

  5. monitoring May 27, 2026, 05:17 PM UTC

    We pushed a large update to our platform which caused temporary read/write disruptions. We have halted all migrations while we investigate and implement safeguards to prevent recurrence. We should be up and running now, but please contact us if you are still experiencing any issues.

  6. investigating May 27, 2026, 05:43 PM UTC

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

  7. investigating May 27, 2026, 05:47 PM UTC

    We are continuing to investigate this issue.

  8. monitoring May 27, 2026, 06:02 PM UTC

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

  9. monitoring May 27, 2026, 08:54 PM UTC

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

  10. resolved May 27, 2026, 10:37 PM UTC

    This incident has been resolved.

  11. postmortem Jun 03, 2026, 03:28 PM UTC

    ### 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]).

Read the full incident report →

Major May 26, 2026 Slow performance across customer hubs 10h 13m ReadMe Hubs, Admin Dashboard

Started May 26, 2026, 05:41 PM UTC· resolved May 27, 2026, 03:54 AM UTC

  1. investigating May 26, 2026, 05:41 PM UTC

    We are experiencing slow performance across customer hubs

  2. monitoring May 26, 2026, 05:49 PM UTC

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

  3. resolved May 27, 2026, 03:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 26, 2026 Degraded performance across Admin Hubs 1h 58m ReadMe Hubs, ReadMe Knowledge Base, Admin Dashboard

Started May 26, 2026, 01:39 PM UTC· resolved May 26, 2026, 03:37 PM UTC

  1. investigating May 26, 2026, 01:39 PM UTC

    We are currently investigating this issue.

  2. monitoring May 26, 2026, 02:26 PM UTC

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

  3. resolved May 26, 2026, 03:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 7, 2026 Issues Creating New Changelogs 3h 34m Admin Dashboard

Started May 07, 2026, 11:43 PM UTC· resolved May 08, 2026, 03:18 AM UTC

  1. investigating May 07, 2026, 11:43 PM UTC

    We are currently investigating an issue creating changelogs

  2. identified May 08, 2026, 12:40 AM UTC

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

  3. monitoring May 08, 2026, 03:02 AM UTC

    We have deployed the fix and are monitoring the results

  4. resolved May 08, 2026, 03:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 28, 2026 Creating branches is resulting in 500 errors 52m ReadMe Hubs

Started Apr 28, 2026, 06:38 PM UTC· resolved Apr 28, 2026, 07:31 PM UTC

  1. investigating Apr 28, 2026, 06:38 PM UTC

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

  2. identified Apr 28, 2026, 07:02 PM UTC

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

  3. resolved Apr 28, 2026, 07:31 PM UTC

    Branches and versions can now be created successfully

Read the full incident report →

Critical April 24, 2026 ReadMe Service Disruption 15m ReadMe Hubs, ReadMe Knowledge Base, Admin Dashboard, Developer Metrics and 2 more

Started Apr 24, 2026, 12:20 PM UTC· resolved Apr 24, 2026, 12:35 PM UTC

  1. investigating Apr 24, 2026, 12:20 PM UTC

    We are currently investigating an issue affecting ReadMe. Some users may experience degraded performance or intermittent errors. Our team is actively looking into this.

Read the full incident report →

Critical April 24, 2026 Service disruption 2h 53m ReadMe Hubs, ReadMe Knowledge Base

Started Apr 24, 2026, 12:17 PM UTC· resolved Apr 24, 2026, 03:11 PM UTC

  1. investigating Apr 24, 2026, 12:17 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 24, 2026, 12:29 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Apr 24, 2026, 01:42 PM UTC

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

  4. resolved Apr 24, 2026, 03:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 22, 2026 Admin downtime 2h ReadMe Hubs, Admin Dashboard

Started Apr 22, 2026, 02:35 PM UTC· resolved Apr 22, 2026, 04:36 PM UTC

  1. investigating Apr 22, 2026, 02:35 PM UTC

    We are currently investigating this issue.

  2. identified Apr 22, 2026, 02:40 PM UTC

    The issue has been identified as a third-party provider. A fix is being implemented.

  3. monitoring Apr 22, 2026, 02:53 PM UTC

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

  4. monitoring Apr 22, 2026, 02:56 PM UTC

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

  5. monitoring Apr 22, 2026, 02:59 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Apr 22, 2026, 04:36 PM UTC

    Issues with admin requests have been resolved.

Read the full incident report →

Minor April 22, 2026 Slow performance, increased 500 errors upon page load 44m ReadMe Hubs, ReadMe Knowledge Base, Admin Dashboard

Started Apr 22, 2026, 02:59 AM UTC· resolved Apr 22, 2026, 03:43 AM UTC

  1. investigating Apr 22, 2026, 02:59 AM UTC

    We are currently investigating performance issues across the platform.

  2. identified Apr 22, 2026, 03:08 AM UTC

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

  3. resolved Apr 22, 2026, 03:43 AM UTC

    Fix has been implemented and performance has stabilized.

Read the full incident report →

Minor April 20, 2026 Increased Admin Response Times 1h 15m Admin Dashboard

Started Apr 20, 2026, 08:05 PM UTC· resolved Apr 20, 2026, 09:20 PM UTC

  1. identified Apr 20, 2026, 08:05 PM UTC

    The admin interface is experiencing slower than expected response times.

  2. monitoring Apr 20, 2026, 09:16 PM UTC

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

  3. resolved Apr 20, 2026, 09:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 16, 2026 Slow performance / 500 error pages 3h 18m ReadMe Hubs

Started Apr 16, 2026, 04:07 PM UTC· resolved Apr 16, 2026, 07:25 PM UTC

  1. investigating Apr 16, 2026, 04:07 PM UTC

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

  2. monitoring Apr 16, 2026, 04:57 PM UTC

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

  3. resolved Apr 16, 2026, 07:25 PM UTC

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

Read the full incident report →

Minor April 15, 2026 Slow page performance 6h 15m ReadMe Hubs

Started Apr 15, 2026, 05:18 PM UTC· resolved Apr 15, 2026, 11:34 PM UTC

  1. investigating Apr 15, 2026, 05:18 PM UTC

    We are currently investigating slow loading pages across our platform

  2. identified Apr 15, 2026, 05:39 PM UTC

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

  3. resolved Apr 15, 2026, 11:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 8, 2026 Discussion posts throwing 500 errors 3h 35m ReadMe Hubs

Started Apr 08, 2026, 06:11 PM UTC· resolved Apr 08, 2026, 09:47 PM UTC

  1. investigating Apr 08, 2026, 06:11 PM UTC

    We are currently investigating the issue. Discussion posts can be edited, but navigating them may result in a 500 error.

  2. resolved Apr 08, 2026, 09:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 31, 2026 Readme high response times. 24m ReadMe Hubs

Started Mar 31, 2026, 09:32 PM UTC· resolved Mar 31, 2026, 09:56 PM UTC

  1. investigating Mar 31, 2026, 09:32 PM UTC

    We are currently investigating this issue.

  2. investigating Mar 31, 2026, 09:41 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 31, 2026, 09:53 PM UTC

    We are continuing to investigate this issue.

  4. investigating Mar 31, 2026, 09:54 PM UTC

    We are continuing to investigate this issue.

  5. resolved Mar 31, 2026, 09:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 30, 2026 Issues with saving MDX 5m ReadMe Hubs

Started Mar 30, 2026, 02:53 PM UTC· resolved Mar 30, 2026, 02:59 PM UTC

  1. investigating Mar 30, 2026, 02:53 PM UTC

    We're currently seeing intermittent errors with saving pages.

  2. identified Mar 30, 2026, 02:56 PM UTC

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

  3. resolved Mar 30, 2026, 02:59 PM UTC

    You should be able to save again!

Read the full incident report →

Minor December 20, 2025 ReadMe Hub Down 1h 23m ReadMe Hubs

Started Dec 20, 2025, 01:40 AM UTC· resolved Dec 20, 2025, 03:03 AM UTC

  1. investigating Dec 20, 2025, 01:40 AM UTC

    We are currently investigating this issue.

  2. investigating Dec 20, 2025, 01:41 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Dec 20, 2025, 02:07 AM UTC

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

  4. monitoring Dec 20, 2025, 02:31 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Dec 20, 2025, 03:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 5, 2025 Dash and Hub Outage 42m ReadMe Hubs, ReadMe Knowledge Base, Admin Dashboard, Cloudflare CDN/Cache

Started Dec 05, 2025, 09:27 AM UTC· resolved Dec 05, 2025, 10:10 AM UTC

  1. monitoring Dec 05, 2025, 09:27 AM UTC

    Our CDN provider (Cloudflare) had an outage causing disruption across all dash and hubs. We're monitoring now but things seem to have started to come back online.

  2. resolved Dec 05, 2025, 10:10 AM UTC

    This has now been resolved upstream.

Read the full incident report →

Major November 18, 2025 Cloudflare outage 1h 41m ReadMe Hubs, ReadMe Knowledge Base, Admin Dashboard, Cloudflare CDN/Cache and 3 more

Started Nov 18, 2025, 01:27 PM UTC· resolved Nov 18, 2025, 03:09 PM UTC

  1. monitoring Nov 18, 2025, 01:27 PM UTC

    Cloudflare is experiencing an outage and we are monitoring the effects on ReadMe https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  2. resolved Nov 18, 2025, 03:09 PM UTC

    This incident has been resolved.

Read the full incident report →