- Level
- confirmed
- Worst impact
- Degraded
- Components
- ReadMe Hubs, ReadMe Knowledge Base, Admin Dashboard, Cloudflare CDN/Cache, Developer Metrics, Cloudflare SSL for SaaS Provisioning, Owlbot AI, ReadMe Micro
- Down Index
- 34of 100
What to do
Check whether you use ReadMe ReadMe Hubs, ReadMe Knowledge Base, Admin Dashboard, Cloudflare CDN/Cache and 4 more. 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 2h 4m it lasted.
Anything that failed between 2025-06-12 19:25 UTC and 2025-06-12 21:29 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 2
- monitoring
While ReadMe services have not been affected, our team is monitoring the status of widespread outages with Cloudflare and GCS.
provider
- resolved
ReadMe services were not affected by the incidents at Cloudflare and Google Cloud, which are now reporting as fully operational.
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-658f4cff90
Is ReadMe still down?
No, this incident was resolved 2025-06-12 21:29 UTC. For ReadMe's live state, see https://down.guide/readme.
How long did it last?
2h 4m, from 2025-06-12 19:25 UTC to 2025-06-12 21:29 UTC, by the times ReadMe posted.
What was affected?
ReadMe named ReadMe Hubs, ReadMe Knowledge Base, Admin Dashboard, Cloudflare CDN/Cache and 4 more.
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.