ReadMe reported this major-impact incident on its official status page on Jun 24, 2025, 10:27 UTC. It was resolved after 13h 5m.
Right now ReadMe is operational. Live ReadMe status →
We've validated our infrastructure changes and are marking the incident as resolved.
We have deployed changes to our infrastructure and performance is holding steady. Our engineers will continue to monitor systems to guarantee overall stability.
ReadMe Refactored projects are back up as cache is refreshed. We are aware of the cause and are implementing a permanent fix.
ReadMe Refactored projects are currently down and returning errors; our team is actively working on a solution.
A temporary fix has been applied to our cache infrastructure. We will be applying more permanent fixes in the background while we monitor the situation.
We are currently investigating downtime across some hubs. This appears to be the same issue as yesterday, we are actively working on resolving.
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