• On February 20, 2026, at 17:48 UTC, Cloudflare experienced a service outage when a subset of customers who use Cloudflareâs Bring Your Own IP (BYOIP) service saw their routes to the Internet withdrawn via Border Gateway Protocol (BGP). • The issue was not caused, directly or indirectly, by a cyberattack or malicious activity of any kind. • This issue was caused by a change that Cloudflare made to how our network manages IP addresses onboarded through the BYOIP pipeline. • This change caused Cloudflare to unintentionally withdraw customer prefixes. • For some BYOIP customers, this resulted in their services and applications being unreachable from the Internet, causing timeouts and failures to connect across their Cloudflare deployments that used BYOIP. • The website for Cloudflareâs recursive DNS resolver (1.1.1.1) saw 403 errors as well.

Article Summaries:

  • On February 20, 2026, Cloudflare suffered a 6‑hour outage when a change to its Bring Your Own IP (BYOIP) pipeline caused the company to unintentionally withdraw customer prefixes via BGP. The incident, unrelated to any cyberattack, left about 1,100 prefixes-roughly 25 % of all BYOIP routes-unadvertised, making affected services unreachable and generating 403 errors on the 1.1.1.1 DNS resolver. Cloudflare engineers reversed the change, restoring most prefixes by 20:20 UTC, and manually reinstated the remaining 300. Customers could also re‑advertise their IPs through the dashboard. The company apologized and pledged measures to prevent similar outages.

Sources: