- Level
- confirmed
- Worst impact
- Degraded
- Components
- ReadMe Hubs
- Down Index
- 22of 100
What to do
Check whether you use ReadMe ReadMe Hubs. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 18m it lasted.
Anything that failed between 2026-04-16 16:07 UTC and 2026-04-16 19:25 UTC may need a replay.Subscribe to ReadMe's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=readme works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from ReadMe 3
- investigating
We are getting reports of slow performance and 500 errors when loading pages
provider
- monitoring
We've stabilized our platform and our response times have improved. We are currently monitoring the situation.
provider
- resolved
Performance has stabilized and we are no longer returning errors upon loading pages.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-43d76a3c33
Is ReadMe still down?
No, this incident was resolved 2026-04-16 19:25 UTC. For ReadMe's live state, see https://down.guide/readme.
How long did it last?
3h 18m, from 2026-04-16 16:07 UTC to 2026-04-16 19:25 UTC, by the times ReadMe posted.
What was affected?
ReadMe named ReadMe Hubs.
What caused it?
ReadMe hasn't published a root cause. If it does, it shows here.
Where does this come from?
ReadMe's official status page, https://www.readmestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.