- Level
- confirmed
- Worst impact
- Degraded
- Components
- ReadMe Hubs, Admin Dashboard
- Down Index
- 26of 100
What to do
Check whether you use ReadMe ReadMe Hubs, Admin Dashboard. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 7h 44m it lasted.
Anything that failed between 2025-09-19 16:31 UTC and 2025-09-20 00:15 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 7
- investigating
We are currently investigating this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- identified
The issue has been identified and we are currently working on a fix.
provider
- identified
The team has developed a fix and are verifying and deploying it
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
This incident has been resolved.
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-025dcfd83d
Is ReadMe still down?
No, this incident was resolved 2025-09-20 00:15 UTC. For ReadMe's live state, see https://down.guide/providers/readme.
How long did it last?
7h 44m, from 2025-09-19 16:31 UTC to 2025-09-20 00:15 UTC, by the times ReadMe posted.
What was affected?
ReadMe named ReadMe Hubs, Admin Dashboard.
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.