• 25‑minute BGP route leak from Miami router due to automated policy misconfiguration. • Only IPv6 prefixes leaked, affecting Cloudflare customers and external networks. • Congestion, packet loss, and higher latency observed across Miami backbone links. • Firewall filters discarded mis‑routed traffic, limiting impact to Cloudflare services. • Cloudflare publicly apologized and logged the event on Cloudflare Radar. • Incident highlights importance of strict BGP policy validation and monitoring.
Article Summaries:
- On January 22, 2026, an automated routing policy configuration error caused us to leak some Border Gateway Protocol (BGP) prefixes unintentionally from a router at our data center in Miami, Florida. While the route leak caused some impact to Cloudflare customers, multiple external parties were also affected because their traffic was accidentally funnelled through our Miami data center location. The route leak lasted 25 minutes, causing congestion on some of our backbone infrastructure in Miami, elevated loss for some Cloudflare customer traffic, and higher latency for traffic across these link
- On January 22, 2026, a mis‑configured automated routing policy on a Cloudflare router in Miami triggered a 25‑minute BGP route leak that redistributed IPv6 prefixes to transit providers and peers. The leak caused congestion on Cloudflare’s backbone, elevated packet loss for some Cloudflare customers, and higher latency for traffic routed through the Miami data center. Firewall filters discarded some of the mis‑advertised traffic. Cloudflare identified the issue at 20:40 UTC, manually reverted the change at 20:50 UTC, and paused automation on the router. The company apologized to affected users, customers, and networks.
Sources: