CyberHappenings logo
☰
Home Browse Watchlists Experimental About

Track cybersecurity events as they unfold. Sourced timelines. Filter, sort, and browse. Fast, privacy‑respecting. No invasive ads, no tracking.

Cloudflare BGP Route Leak Due to Misconfiguration

First reported
Last updated
1 unique sources, 1 articles

Summary

Hide ▲

Cloudflare experienced a 25-minute BGP route leak on January 22, 2026, affecting IPv6 traffic. The misconfiguration caused congestion, packet loss, and approximately 12 Gbps of dropped traffic. The incident was due to an accidental policy misconfiguration on a router, which led to a mixture of Type 3 and Type 4 route leaks. Cloudflare detected and resolved the issue within 25 minutes by manually reverting the configuration and pausing automation. The root cause was a policy change intended to prevent Miami from advertising Bogotá IPv6 prefixes, which made the export policy overly permissive. Cloudflare has proposed measures to prevent such occurrences in the future, including stricter community-based export safeguards and improved early detection.

Timeline

  1. 26.01.2026 19:50 1 articles · 23h ago

    Cloudflare BGP Route Leak Due to Misconfiguration

    On January 22, 2026, Cloudflare experienced a 25-minute BGP route leak affecting IPv6 traffic. The misconfiguration caused congestion, packet loss, and approximately 12 Gbps of dropped traffic. The incident was due to an accidental policy misconfiguration on a router, which led to a mixture of Type 3 and Type 4 route leaks. Cloudflare detected and resolved the issue within 25 minutes by manually reverting the configuration and pausing automation. The root cause was a policy change intended to prevent Miami from advertising Bogotá IPv6 prefixes, which made the export policy overly permissive. Cloudflare has proposed measures to prevent such occurrences in the future, including stricter community-based export safeguards and improved early detection.

    Show sources
    Open in new tab

Information Snippets

  • The BGP route leak occurred on January 22, 2026, and lasted for 25 minutes.

    First reported: 26.01.2026 19:50
    1 source, 1 article
    Show sources

  • The incident caused congestion, packet loss, and approximately 12 Gbps of dropped traffic.

    First reported: 26.01.2026 19:50
    1 source, 1 article
    Show sources

  • The root cause was a policy change intended to prevent Miami from advertising Bogotá IPv6 prefixes.

    First reported: 26.01.2026 19:50
    1 source, 1 article
    Show sources

  • Cloudflare detected and resolved the issue by manually reverting the configuration and pausing automation.

    First reported: 26.01.2026 19:50
    1 source, 1 article
    Show sources

  • Cloudflare has proposed measures to prevent such occurrences in the future, including stricter community-based export safeguards and improved early detection.

    First reported: 26.01.2026 19:50
    1 source, 1 article
    Show sources