ReadMe incident: ReadMe docs producing 404 errors after reordering and branch merge

Affected components

• Admin Dashboard
• ReadMe Hubs

1. resolvedSep 20, 2025, 00:15 UTC

   This incident has been resolved.

2. monitoringSep 20, 2025, 00:15 UTC

   We are continuing to monitor for any further issues.

3. monitoringSep 19, 2025, 22:31 UTC

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

4. identifiedSep 19, 2025, 20:29 UTC

   The team has developed a fix and are verifying and deploying it

5. identifiedSep 19, 2025, 18:21 UTC

   The issue has been identified and we are currently working on a fix.

6. investigatingSep 19, 2025, 17:21 UTC

   We are continuing to investigate this issue.

7. investigatingSep 19, 2025, 16:31 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.

• 1Password: Email invites to some users are not being received for some customersMinor · Sep 18, 2025, 20:19 UTC
• Pusher: Higher latency on our AP1 cluster for some customersMinor · Sep 19, 2025, 21:15 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