ReadMe reported this major-impact incident on its official status page on May 28, 2026, 14:35 UTC. It was resolved after 4d 3h.
Right now ReadMe is operational. Live ReadMe status →
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.
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.
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.
Systems remain stable. Improvements and fixes have been rolled out and we are continuing to monitor.
Systems appear stable and we are actively rolling out a series of fixes. We will continue to monitor and provide updates
We are receiving reports of degraded performance and are actively investigating. We will provide updates as more information becomes available.
We are continuing to monitor for any further issues.
A fix has been implemented and we are monitoring the results.
Systems are getting back up. We're continuing to work on a permanent fix for this issue.
The issue has been identified and a fix is being implemented.
We're actively investigating this issue.
Our 5-minute checks didn't record a change in ReadMe's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
ReadMe reported 4 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 30m. See ReadMe's uptime and incident history