Minor impactResolvedDevOps

ReadMe incident: Slow performance, increased 500 errors upon page load

ReadMe reported this minor-impact incident on its official status page on Apr 22, 2026, 02:59 UTC. It was resolved after 44 min.

Right now ReadMe is operational. Live ReadMe status →

🔔 Get alerted when ReadMe has issuesFree · email alerts · no credit card
Apr 22, 2026, 02:59 UTC
started
Apr 22, 2026, 03:43 UTC
resolved
44 min
duration
Minor
impact

Affected components

  • Admin Dashboard
  • ReadMe Hubs
  • ReadMe Knowledge Base

Timeline

updates from ReadMe's status page ↗
  1. resolvedApr 22, 2026, 03:43 UTC

    Fix has been implemented and performance has stabilized.

  2. identifiedApr 22, 2026, 03:08 UTC

    We've discovered the issue and have implemented a quick fix

  3. investigatingApr 22, 2026, 02:59 UTC

    We are currently investigating performance issues across the platform.

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

← Previous: Increased Admin Response Times (Apr 20, 2026)Next: Admin downtime (Apr 22, 2026) →
ReadMe incident on Apr 22, 2026: Slow performance, increased 500 errors upon page load · APIStatus.watch