Major impactResolvedDevOps

ReadMe outage: Readme high response times.

ReadMe reported this major-impact incident on its official status page on Mar 31, 2026, 21:32 UTC. It was resolved after 24 min.

Right now ReadMe is operational. Live ReadMe status →

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

Mar 31, 2026, 21:32 UTC

started

Mar 31, 2026, 21:56 UTC

resolved

24 min

duration

Major

impact

Affected components

ReadMe Hubs

Timeline

updates from ReadMe's status page ↗

resolvedMar 31, 2026, 21:56 UTC
This incident has been resolved.
investigatingMar 31, 2026, 21:54 UTC
We are continuing to investigate this issue.
investigatingMar 31, 2026, 21:53 UTC
We are continuing to investigate this issue.
investigatingMar 31, 2026, 21:41 UTC
We are continuing to investigate this issue.
investigatingMar 31, 2026, 21:32 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.

Smartsheet: Proof Performance and WatermarksMinor · Mar 31, 2026, 18:53 UTC
npm: Degraded Performance in View Package and Login on npmjs.comMinor · Mar 31, 2026, 19:12 UTC
1Password: Individual and Family accounts are unable to access Developer EnvironmentsMinor · Mar 31, 2026, 21:28 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: Issues with saving MDX (Mar 30, 2026)Next: Discussion posts throwing 500 errors (Apr 8, 2026) →