ReadMe outage: Discussion posts throwing 500 errors

Affected components

• ReadMe Hubs

1. resolvedApr 8, 2026, 21:47 UTC

   This incident has been resolved.

2. investigatingApr 8, 2026, 18:11 UTC

   We are currently investigating the issue. Discussion posts can be edited, but navigating them may result in a 500 error.

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
• Render: Disruption affecting the provisioning of new instances in Singapore and partially in OregonMajor · Apr 8, 2026, 09:57 UTC
• Intercom: Email Forwarding is experiencing difficultiesMajor · Apr 8, 2026, 18:22 UTC
• CircleCI: Delays in Workflow and Job data in the Usage APIMinor · Apr 8, 2026, 13:20 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