ReadMe incident: Degraded performance across Admin Hubs

Affected components

• Admin Dashboard
• ReadMe Hubs
• ReadMe Knowledge Base

1. resolvedMay 12, 2026, 21:10 UTC

   This incident has been resolved.

2. monitoringMay 12, 2026, 19:38 UTC

   A fix has been implemented and we are monitoring the results.

3. identifiedMay 12, 2026, 14:15 UTC

   We are investigating slowness across 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.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Akamai: Bot Manager Premier IssuesMinor · May 11, 2026, 16:03 UTC
• Netlify: Increased Latency in API & BuildsMinor · May 12, 2026, 14:30 UTC
• Linode: Connectivity Issue - AP-West (Mumbai) and IN-MAA (Chennai)Minor · May 12, 2026, 17:12 UTC
• Akamai: Edge Delivery Issues between India and EuropeMinor · May 12, 2026, 18:39 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