Cloudflare·20 Feb 2026 · 17:48 UTCResolved

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.

Reported duration6h 07m
Impact scopeWidespread
Incident categoryNetwork routing
WHAT HAPPENED

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.

ROOT CAUSE

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.

AFFECTED SURFACE

Services and systems

BYOIPCore CDNMagic TransitSpectrumDedicated Egress1.1.1.1 website

Reported scope: Global · affected BYOIP prefixes

EVENT TIMELINE

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).

  1. 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.

  2. 20:20 UTC Local conversion unavailable: source time is not normalized

    Most prefixes restored

    Cloudflare reports that roughly 800 prefixes were restored.

  3. 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.

COMMUNITY SIGNAL

What did this incident feel like?

React anonymously. Counts are shared across visitors and are not a measure of the number of customers affected.

Community signal
Shared anonymous reactions