ReadMe incident: Degraded performance across Admin Hubs

Affected components

• Admin Dashboard
• ReadMe Hubs
• ReadMe Knowledge Base

1. resolvedMay 11, 2026, 18:34 UTC

   This incident has been resolved.

2. monitoringMay 11, 2026, 17:08 UTC

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

3. identifiedMay 11, 2026, 16:03 UTC

   The issue has been identified and a fix is being implemented.

4. investigatingMay 11, 2026, 15:43 UTC

   We are currently investigating this issue.

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
• Clerk: Account Portal not RedirectingMajor · May 11, 2026, 15:00 UTC
• Upstash: Fly.io Upstash Redis service distruption (FRA region)Major · May 11, 2026, 15:05 UTC
• OneSignal: Dashboard & API - Partial OutageMajor · May 11, 2026, 18:19 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Snyk: Snyk Recurring Tests DelayedMinor · May 6, 2026, 15:32 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Akamai: Bot Manager Premier IssuesMinor · May 11, 2026, 16:03 UTC
• Render: Degraded builds/deploys (all regions)Minor · May 11, 2026, 17:07 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