- Level
- confirmed
- Worst impact
- Degraded
- Components
- Bring Your Own IP (BYOIP)
- Down Index
- 11of 100
What to do
Check whether you use Cloudflare Bring Your Own IP (BYOIP). 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 3m it lasted.
Anything that failed between 2026-09-24 10:22 UTC and 2026-09-24 10: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
This incident has now been resolved - Customers with BYOIP addresses were unable to update their BGP prefixes, including advertising or withdrawing prefixes. Customers making changes to their address maps may also have experienced delays.
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-0bdf468824
Is Cloudflare still down?
No, this incident was resolved 2026-09-24 10:25 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.
How long did it last?
3m, from 2026-09-24 10:22 UTC to 2026-09-24 10:25 UTC, by the times Cloudflare posted.
What was affected?
Cloudflare named Bring Your Own IP (BYOIP).
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.