- Level
- confirmed
- Worst impact
- Degraded
- Components
- Network, Chicago, United States - (ORD)
- Regions
- us
Summary
Cloudflare says it experienced network performance issues in Chicago between 04:55 and 05:12 UTC. The provider says the incident is resolved.
Written by anthropic/claude-haiku-5.5 from Cloudflare's own updates.
What to do
Check whether you use Cloudflare Network, Chicago, United States - (ORD) in us. 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 17m it lasted.
Anything that failed between 2026-11-07 04:55 UTC and 2026-11-07 05:12 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 04:55-05:12 UTC 7th Dec Cloudflare experienced issues with network performance in Chicago.
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-c59e48b7ca
Is Cloudflare still down?
No, this incident was resolved 2026-11-07 05:12 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.
How long did it last?
17m, from 2026-11-07 04:55 UTC to 2026-11-07 05:12 UTC, by the times Cloudflare posted.
What was affected?
Cloudflare named Network, Chicago, United States - (ORD) in us.
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.