ReadMe outage: Slow performance across customer hubs

Affected components

• Admin Dashboard
• ReadMe Hubs

1. resolvedMay 27, 2026, 03:54 UTC

   This incident has been resolved.

2. monitoringMay 26, 2026, 17:49 UTC

   We have identified and quickly fixed the issue and are currently investigating a more thorough fix

3. investigatingMay 26, 2026, 17:41 UTC

   We are experiencing slow performance across customer hubs

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.

• Inngest: Issues connecting to data store for events/runs/metrics pagesMajor · May 26, 2026, 09:26 UTC
• LiveKit: Partial data outage on LiveKit Cloud DashboardMajor · May 26, 2026, 19:53 UTC
• Clerk: Elevated 500 rates on API responsesMajor · May 26, 2026, 21:19 UTC
• Inngest: Downstream provider causing dashboard loading errorsMajor · May 26, 2026, 21:31 UTC
• Elasticsearch: Missing Metrics in Cloud Console - Azure Southeast AsiaMajor · May 26, 2026, 21:35 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · May 19, 2026, 10:13 UTC
• Convex: Custom domain creation encountering errorsMinor · May 26, 2026, 17:48 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