Critical impactResolvedDevOps

ReadMe outage: ReadMe Hubs are down

ReadMe reported this critical-impact incident on its official status page on Mar 10, 2025, 13:12 UTC. It was resolved after 1h 25m.

Right now ReadMe is operational. Live ReadMe status →

🔔 Get alerted when ReadMe has issuesFree · email alerts · no credit card

Mar 10, 2025, 13:12 UTC

started

Mar 10, 2025, 14:37 UTC

resolved

1h 25m

duration

Critical

impact

Affected components

ReadMe Hubs

Timeline

updates from ReadMe's status page ↗

resolvedMar 10, 2025, 14:37 UTC
We have added server capacity to deal with an increase in traffic and load. We will continue to monitor but all sites appear to be working as expected again. Please reach out to [email protected] if you are still having problems.
monitoringMar 10, 2025, 13:26 UTC
A fix has been implemented and we are monitoring the results.
investigatingMar 10, 2025, 13:23 UTC
We are continuing to investigate this issue.
investigatingMar 10, 2025, 13:12 UTC
We are currently investigating the issue

What APIStatus.watch saw

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.

How often does ReadMe have incidents?

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

← Previous: Slow performance across all hubs and dashboard (Mar 5, 2025)Next: ReadMe Hubs are down (Mar 24, 2025) →