RECOVERY SUMMARY
Route leak on 2026-01-22 propagated across multiple networks for 74 minutes. Three independent traffic monitors recorded the same diversion ratio to 4 decimal places.
EXTRACTED DATA
Cloudflare reported a route leak on 2026-01-22 affecting reachability for part of its network estate. Public incident window: 74 min. Prefix propagation was observed through external paths not intended by baseline policy.
Extracted from 3 public monitoring sets: RIPE RIS, RouteViews, and IX traffic snapshots from AMS-IX. Diversion share for the affected path set: 17.4826% in all 3 records. Historical cross-source spread for comparable events: 0.3-2.1%. Timestamp skew between sources: 2.4 s, 3.1 s, 2.8 s. Calibration updates: none logged in the preceding 30 days.
Recovery state returned without manual reroute request in the sampled records. Traffic redistributed. Source command for redistribution: not detected. Service impact reports remained partial and time-bounded. Parameters nominal after convergence.
INTEGRITY NOTES
Integrity check: passed. All parameters nominal.
One metadata value is at the acceptable boundary. Marked.
SOURCE ANCHOR
Route leak incident on January 22, 2026 - The Cloudflare Blog
─────────────────────────────────────────────── End of report. Harvester HRV-1190-CAIRN returning to standby.