Critical impactResolvedDevOps

ReadMe outage: Service disruption

ReadMe reported this critical-impact incident on its official status page on Apr 24, 2026, 12:17 UTC. It was resolved after 2h 54m.

Right now ReadMe is operational. Live ReadMe status →

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

Apr 24, 2026, 12:17 UTC

started

Apr 24, 2026, 15:11 UTC

resolved

2h 54m

duration

Critical

impact

Affected components

ReadMe Hubs
ReadMe Knowledge Base

Timeline

updates from ReadMe's status page ↗

resolvedApr 24, 2026, 15:11 UTC
This incident has been resolved.
monitoringApr 24, 2026, 13:42 UTC
A fix has been implemented and we are monitoring the results.
investigatingApr 24, 2026, 12:29 UTC
We are continuing to investigate this issue.
investigatingApr 24, 2026, 12:17 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.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
Inngest: Degraded performance for REST API (runs/events data)Minor · Apr 23, 2026, 20:06 UTC
Netlify: Increased Errors on Image CDNMinor · Apr 24, 2026, 14:10 UTC

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: Admin downtime (Apr 22, 2026)Next: Creating branches is resulting in 500 errors (Apr 28, 2026) →