Cloudflare BYOIP routes withdrawn from the Internet
A network-address management change unintentionally withdrew customer IP prefixes, making some customer applications unreachable from the public Internet.
Incident summary
A network-address management change unintentionally withdrew customer IP prefixes, making some customer applications unreachable from the public Internet.
Affected customers using the impacted BYOIP advertisements saw connection failures and timeouts. Cloudflare also reported HTTP 403 errors on the 1.1.1.1 website; DNS resolution through the public resolver was not affected.
What the provider reported
A change to the BYOIP address-management pipeline caused Cloudflare to withdraw customer BGP prefixes. The provider reported that about 1,100 prefixes were withdrawn before the change was stopped and configurations restored.
Editorial note: This is a concise summary of the provider’s public explanation, not an independent technical investigation.
Services and systems
Reported scope: Global · affected BYOIP prefixes
Latest source updates
Showing up to the 3 latest updates available in the source record. UTC is fixed; local time is converted in this browser (your local timezone).
- 17:56–18:46 UTC Local conversion unavailable: source time is not normalized
Prefixes withdrawn
Cloudflare reports that approximately 1,100 prefixes were withdrawn during this window.
- 20:20 UTC Local conversion unavailable: source time is not normalized
Most prefixes restored
Cloudflare reports that roughly 800 prefixes were restored.
- 23:03 UTC Local conversion unavailable: source time is not normalized
Remaining prefixes restored
Engineers manually restore the remaining affected prefixes; the full incident duration was 6 hours and 7 minutes.
What did this incident feel like?
React anonymously. Counts are shared across visitors and are not a measure of the number of customers affected.