- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
What to do
Check whether you use Cloudflare 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 50m it lasted.
Anything that failed between 2026-10-18 08:00 UTC and 2026-10-18 08:50 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
Due to unexpected prefix withdrawals on peering links in IAD and CMH (Ashburn, Virginia and Columbus, Ohio, in the United States) on an external provider, customers experienced increased latency and timeouts from 08:00 to 08:50 UTC. Services have fully normalized following the restoration of prefix advertisements.
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-036a069135
Is Cloudflare still down?
No, this incident was resolved 2026-10-18 08:50 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.
How long did it last?
50m, from 2026-10-18 08:00 UTC to 2026-10-18 08:50 UTC, by the times Cloudflare posted.
What was affected?
Cloudflare named 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.