Critical impactResolvedDevOps

ReadMe outage: We are investigating widespread downtime across all hubs

ReadMe reported this critical-impact incident on its official status page on Jun 23, 2025, 14:16 UTC. It was resolved after 1h 32m.

Right now ReadMe is operational. Live ReadMe status →

🔔 Get alerted when ReadMe has issuesFree · email alerts · no credit card
Jun 23, 2025, 14:16 UTC
started
Jun 23, 2025, 15:48 UTC
resolved
1h 32m
duration
Critical
impact

Affected components

  • ReadMe Hubs

Timeline

updates from ReadMe's status page ↗
  1. resolvedJun 23, 2025, 15:48 UTC

    This incident has been resolved.

  2. monitoringJun 23, 2025, 15:37 UTC

    We've identified the root cause of the issue: a cold cache, which temporarily prevented some pages from loading. The cache is regenerating, and things are coming back to normal.

  3. monitoringJun 23, 2025, 14:19 UTC

    We are continuing to monitor for any further issues.

  4. monitoringJun 23, 2025, 14:16 UTC

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

  5. investigatingJun 23, 2025, 14:16 UTC

    We have identified a likely cause and are working on remediating.

  6. investigatingJun 23, 2025, 13:29 UTC

    We are currently investigating and will update as/when we know more.

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 and Dashboard are down (May 30, 2025)Next: ReadMe hubs are down (Jun 23, 2025) →
ReadMe outage on Jun 23, 2025: We are investigating widespread downtime across all hubs · APIStatus.watch