- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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 0m it lasted.
Anything that failed between 2026-01-04 21:20 UTC and 2026-01-04 21:20 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
Cloudflare has resolved an issue regarding network performance in Queretaro, MX. The incident occurred between 20:26 and 20:50 UTC. Performance has returned to baseline levels, and we are continuing to monitor the region to ensure stability.
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-5bfa01a66c
Is Cloudflare still down?
No, this incident was resolved 2026-01-04 21:20 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.
How long did it last?
0m, from 2026-01-04 21:20 UTC to 2026-01-04 21:20 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.