ReadMe incident: Degraded performance due to third-party infrastructure issues

Affected components

• Admin Dashboard
• ReadMe Hubs

1. resolvedJul 24, 2026, 13:37 UTC

   This incident has been resolved.

2. monitoringJul 24, 2026, 12:22 UTC

   Experiencing degraded performance due to third-party infrastructure issues. We are monitoring this situation and working to maintain stability on our end.

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.

• Render: Service Disruption in OregonCritical · Jul 24, 2026, 11:16 UTC
• OVHcloud: [EU-WEST-PAR][Storage] - Object storage S3 Standard Incident NotificationMajor · Jul 23, 2026, 19:14 UTC
• Grafana Cloud: Errors creating new Slack integration for Grafana IRMMajor · Jul 24, 2026, 09:17 UTC
• Notion: Notion is downMajor · Jul 24, 2026, 11:24 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• dbt Cloud: Scheduled jobs are intermittently affected by job failures caused by 403 errorMinor · Jul 24, 2026, 07:58 UTC
• DigitalOcean: Network Connectivity from India to NYCMinor · Jul 24, 2026, 10:36 UTC
• Akamai: Edge Delivery IssuesMinor · Jul 24, 2026, 12:21 UTC
• Mailgun: Route delays in EU RegionMinor · Jul 24, 2026, 12:27 UTC
• ClickHouse Cloud: Monitoring and billing impact on customer services in ap-southeast-1Minor · Jul 24, 2026, 13: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