Cloudflare route leak causes Miami backbone congestion
An automated routing-policy configuration error leaked IPv6 routes from a Miami data center, temporarily funneling traffic through infrastructure not intended to carry it.
Incident summary
An automated routing-policy configuration error leaked IPv6 routes from a Miami data center, temporarily funneling traffic through infrastructure not intended to carry it.
The 25-minute route leak caused congestion on parts of Cloudflare’s Miami backbone, packet loss for some customer traffic, and higher latency across affected links. External networks were also affected.
What the provider reported
Cloudflare attributed the event to an accidental router misconfiguration in its routing-policy automation. The issue affected IPv6 traffic only.
Editorial note: This is a concise summary of the provider’s public explanation, not an independent technical investigation.
Services and systems
Reported scope: Miami, Florida · IPv6 traffic
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).
- 22 Jan 2026 Local conversion unavailable: source time is not normalized
Route leak begins
An automated routing-policy configuration error leaks IPv6 prefixes from a Miami router.
- 25 minutes later Local conversion unavailable: source time is not normalized
Incident ends
The route leak is withdrawn; the provider reports congestion, packet loss, and elevated latency during the event.
- No source clock time published
Provider postmortem published
Cloudflare publishes its analysis of the routing-policy error and its impact on Miami IPv6 traffic; no publication clock time was provided.
What did this incident feel like?
React anonymously. Counts are shared across visitors and are not a measure of the number of customers affected.