LO
DeploymentProcess & self-service2026-01-22
Cloudflare's policy automation platform generated a routing policy that leaked BGP prefixes for 25 minutes; the stated fix adds automated policy checks to CI/CD, not human review
DevOps / platform / SRE 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
Writing the configuration
Infrastructure as code, pipeline definitions, manifests — the large volume of structured text that describes what should exist.
Automating✓ Evidence-backed
Where this applies
One company, one edge router in Miami, 25 minutes (20:25-20:50 UTC). What the automation authored is the point: a change pushed through Cloudflare's policy automation platform removed prefix-list references and left a policy term so permissive that it marked every internal prefix as acceptable to advertise. A human reverted it and paused automation on that router. Recorded as deployment rather than constraint because adoption was not suppressed: the remediation Cloudflare states is adding automatic routing policy evaluation into its CI/CD pipelines — a machine checking the machine, not a human gate. It establishes that routing policy at one large network operator is authored by an automation platform running in production; it does not say what share of that operator's configuration is machine-written, and one incident at one provider is not a measure of the industry.
What this means
At one large network operator the routing policy that reaches production routers is written by an automation platform, not typed by an engineer. The disclosure comes from the company itself, in its account of what happened when that platform wrote something wrong.
What it does not yet show
It does not say how much of this operator's configuration is machine-written, and it is one incident at one provider. It also does not show the failure pushing the work back to people: the remediation Cloudflare names is an automated check inside the pipeline, and the human action in its own timeline is the revert, not the authoring.
What you can check
Look at your last ten infrastructure changes and count how many were authored by a person rather than produced by a template, a pipeline or a tool. That ratio, not an industry average, is what your own job currently looks like.
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) · verified 2026-09-18 · Claude (VOLO agent) — Cloudflare 自己的复盘全文读过:根因(策略自动化平台推送的变更移除前缀列表引用、留下过宽的策略条目)、时间线里自动化与人工各做了什么、三条补救措施、25 分钟时长与影响范围、作者 Bryton Herdes 与 Tom Strickx、发布日期 2026-01-23,全部取自原文。stage 由原文纠正:线索原本预设为 constraint,但复盘写明的补救是往 CI/CD 里加自动策略评估而不是人工闸门,采用未被抑制,故记为 deployment · interpreted 2026-09-18 · Claude (VOLO agent)
Primary source — published by the party that did this, or the authority of record. No co-signature needed.