Minor impactResolvedDevOps

ReadMe incident: Slow performance / 500 error pages

ReadMe reported this minor-impact incident on its official status page on Apr 16, 2026, 16:07 UTC. It was resolved after 3h 18m.

Right now ReadMe is operational. Live ReadMe status →

🔔 Get alerted when ReadMe has issuesFree · email alerts · no credit card
Apr 16, 2026, 16:07 UTC
started
Apr 16, 2026, 19:25 UTC
resolved
3h 18m
duration
Minor
impact

Affected components

  • ReadMe Hubs
  1. resolvedApr 16, 2026, 19:25 UTC

    Performance has stabilized and we are no longer returning errors upon loading pages.

  2. monitoringApr 16, 2026, 16:57 UTC

    We've stabilized our platform and our response times have improved. We are currently monitoring the situation.

  3. investigatingApr 16, 2026, 16:07 UTC

    We are getting reports of slow performance and 500 errors when loading pages

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.

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

ReadMe incident on Apr 16, 2026: Slow performance / 500 error pages · APIStatus.watch