- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 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 1h 33m it lasted.
Anything that failed between 2026-01-08 18:51 UTC and 2026-01-08 20:25 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
A recent software update inadvertently altered the ordering of DNS records within our cached responses. Specifically, the sequence of CNAME and non-CNAME records in the "answer" section was changed, which conflicted with the expectations of certain DNS client implementations. Upon identifying this behavior, we reverted the release to restore standard record ordering and resolve connectivity issues for affected users.
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-af1e73f317
Is Cloudflare still down?
No, this incident was resolved 2026-01-08 20:25 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.
How long did it last?
1h 33m, from 2026-01-08 18:51 UTC to 2026-01-08 20:25 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.