Route leak incident on January 22, 2026

Cloudflare caused a BGP route leak on January 22, 2026, due to an automated routing policy misconfiguration at their Miami data center, affecting IPv6 traffic for 25 minutes.

• •A policy change to remove Bogotá (BOG04) prefix lists left a JunOS policy term matching all internal route types, causing IBGP routes to be advertised externally
• •The misconfiguration caused Cloudflare (AS13335) to leak peer routes to other peers and providers, violating valley-free routing (RFC7908 Type 3 and Type 4 leaks)
• •Impact included backbone congestion in Miami, elevated packet loss for Cloudflare customers, and traffic discarded by firewall filters not designed for external traffic
• •The bad config was manually reverted within 25 minutes; automation was paused to prevent re-application
• •BGP updates were publicly observable via MRT files using tools like monocle and RIPE BGPlay