Critical impactResolvedDevOps

ReadMe outage: ReadMe Hubs are down

ReadMe reported this critical-impact incident on its official status page on Mar 24, 2025, 14:08 UTC. It was resolved after 1d 9h.

Right now ReadMe is operational. Live ReadMe status →

🔔 Get alerted when ReadMe has issuesFree · email alerts · no credit card
Mar 24, 2025, 14:08 UTC
started
Mar 25, 2025, 23:21 UTC
resolved
1d 9h
duration
Critical
impact

Affected components

  • ReadMe Hubs

Timeline

updates from ReadMe's status page ↗
  1. resolvedMar 25, 2025, 23:21 UTC

    This incident has been resolved.

  2. investigatingMar 24, 2025, 16:31 UTC

    The hubs are currently operating as expected, but we are actively monitoring and investigating the root cause of this issue. If you are still experiencing any problems, please contact [email protected].

  3. investigatingMar 24, 2025, 14:08 UTC

    We are currently investigating this 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: ReadMe Hubs are down (Mar 10, 2025)Next: Slow performance across hubs (Mar 26, 2025) →
ReadMe outage on Mar 24, 2025: ReadMe Hubs are down · APIStatus.watch