ReadMe incident: Slow page performance

Affected components

• ReadMe Hubs

1. resolvedApr 15, 2026, 23:34 UTC

   This incident has been resolved.

2. identifiedApr 15, 2026, 17:39 UTC

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

3. investigatingApr 15, 2026, 17:18 UTC

   We are currently investigating slow loading pages across our platform

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 in AWS me-south-1 and me-central-1 regionsMajor · Apr 1, 2026, 19:52 UTC
• 1Password: SSO sign-in failing on some attempts for some usersMajor · Apr 13, 2026, 17:24 UTC
• GitBook: Git Sync executions are delayed due to third-party outageMajor · Apr 15, 2026, 15:34 UTC
• Datadog: Delayed MetricsMajor · Apr 15, 2026, 22:38 UTC
• LiveKit: Increased Latency in RoomService APIs, brief period of higher error rateMajor · Apr 15, 2026, 23:23 UTC
• Inngest: Delays in function run schedulingMinor · Apr 15, 2026, 12:15 UTC
• Intercom: Fin is experiencing issuesMinor · Apr 15, 2026, 16:57 UTC
• Amplitude: Event Streaming DelayMinor · Apr 15, 2026, 23:09 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