- Level
- confirmed
- Worst impact
- Degraded
- Components
- Owlbot AI
- Down Index
- 25of 100
What to do
Check whether you use ReadMe Owlbot AI. 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 1d 22h it lasted.
Anything that failed between 2025-09-09 16:47 UTC and 2025-09-11 14:53 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
- investigating
Currently Owlbot AI is experiencing a service degradation/outage. ReadMe engineers have been dispatched and are treating this as a top-priority issue. Projects not utilizing Owlbot AI are not impacted and standard search continues to work correctly.
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-396caa54a1
Is ReadMe still down?
No, this incident was resolved 2025-09-11 14:53 UTC. For ReadMe's live state, see https://down.guide/readme.
How long did it last?
1d 22h, from 2025-09-09 16:47 UTC to 2025-09-11 14:53 UTC, by the times ReadMe posted.
What was affected?
ReadMe named Owlbot AI.
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.