LO
DeploymentCognitive automation2026-01-22
A routing change pushed through Cloudflare's policy automation leaked BGP routes for 25 minutes until a network operator reverted it by hand and paused the automation
Network engineeroccupation page →
Event date / reported
2026-01-22 · reported 2026-01-23
Evidence stage
DeploymentAn employer has put it into production. Can move the baseline — weighted by scale and how similar the setting is.
Tasks this bears on
Configuration and changes
Making configuration changes to routers, switches, firewalls and radio networks, and managing them safely.
Automating✓ Evidence-backed
Where this applies
One operator, one edge router in Miami. Cloudflare's post-mortem says a change pushed via its policy automation platform at 20:25 UTC produced unexpected advertisements to transit providers and peers, that the route leak lasted 25 minutes, and that at 20:50 UTC the bad configuration change was manually reverted by a network operator and automation was paused for the router; its stated remediations include automatic routing-policy evaluation in its CI/CD pipelines. It shows routing policy written and pushed by automation in production, and a person stepping in when it failed; one incident is not a measure of the industry.
What this means
Automated network changes run in production — and when one goes wrong, it is a network operator who reverts it and pauses the automation. The routine change moves to machines; the recovery stays with people.
What it does not yet show
One incident at one operator; it does not measure how often automated changes fail or who fixes them elsewhere.
What you can check
Open Cloudflare's post-mortem "Route leak incident on January 22, 2026" and find "manually reverted by a network operator".
Does it change the assessment?
No. The impact index is never moved by a single event. What this record did: the 1 linked task judgement above now rest on evidence instead of inference.
Source
Cloudflare — Route leak incident on January 22, 2026 (Bryton Herdes, Tom Strickx; January 23, 2026) · verified 2026-09-29 · Claude (VOLO agent) · interpreted 2026-09-29 · Claude (VOLO agent)
Primary source — published by the party that did this, or the authority of record. No co-signature needed.
This record is cited in