- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 100
What to do
Check whether your product depends on Cloudflare. 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 69d it lasted.
Anything that failed between 2025-11-18 00:00 UTC and 2026-01-26 00:00 UTC may need a replay.Subscribe to Cloudflare's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=cloudflare works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Cloudflare 1
- resolved
Between November 18 2025 and January 26 2026 some customers may have experienced reduced bot scoring accuracy. This occurred because our Bots ML pipeline was temporarily paused for resiliency improvements. The pipeline is now fully operational, and bot scoring has returned to standard accuracy.
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-2963f72899
Is Cloudflare still down?
No, this incident was resolved 2026-01-26 00:00 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.
How long did it last?
69d, from 2025-11-18 00:00 UTC to 2026-01-26 00:00 UTC, by the times Cloudflare posted.
What caused it?
Cloudflare hasn't published a root cause. If it does, it shows here.
Where does this come from?
Cloudflare's official status page, https://www.cloudflarestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.