Minor impactResolvedDevOps

ReadMe incident: Degraded Performance Across Hubs

ReadMe reported this minor-impact incident on its official status page on Sep 22, 2026, 14:22 UTC. It was resolved after 2h 22m.

Right now ReadMe is operational. Live ReadMe status →

🔔 Get alerted when ReadMe has issuesFree · email alerts · no credit card
Sep 22, 2026, 14:22 UTC
started
Sep 22, 2026, 16:44 UTC
resolved
2h 22m
duration
Minor
impact

Affected components

  • Admin Dashboard
  • ReadMe Hubs
  • ReadMe Knowledge Base
  1. resolvedSep 22, 2026, 16:44 UTC

    This incident has been resolved.

  2. monitoringSep 22, 2026, 15:16 UTC

    We are continuing to monitor for any further issues.

  3. monitoringSep 22, 2026, 15:03 UTC

    We've identified additional contributing factors and are actively working to fix them.

  4. monitoringSep 22, 2026, 14:41 UTC

    A fix has been implemented and we're currently monitoring the results. Performance should be returning to normal.

  5. investigatingSep 22, 2026, 14:22 UTC

    We're currently investigating elevated latency and slow response times affecting hubs. Actively working to identify the root cause and restore normal service.

What APIStatus.watch saw

  • Sep 22, 2026, 14:25 UTCoperational → degraded
  • Sep 22, 2026, 16:45 UTCdegraded → operational

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 Sep 22, 2026: Degraded Performance Across Hubs · APIStatus.watch