LO
DeploymentCognitive automation2026-06-24
Verizon's closed-loop automation executed over 70 million network configuration changes autonomously in 2025, its chief technology officer wrote
Network engineeroccupation page →
Event date / reported
2026-06-24
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
Troubleshooting and outages
Detecting faults, finding the root cause of outages and restoring service.
Being augmented✓ Evidence-backed
Where this applies
United States, Verizon's network. The company's CTO writes that in 2025 its closed-loop automation platforms executed over 70 million network configuration changes autonomously, that implemented by hand these changes would have required thousands of technicians working around the clock, and that issues which took engineering teams hours to diagnose and correct are now identified and resolved in less than two minutes. It is the operator describing its own systems; the 'thousands of technicians' is its counterfactual, not a count of jobs changed.
What this means
At one of the largest carriers, routine network changes are made by software at a scale no team could match. The engineer's role shifts to setting the limits of that automation and handling what it cannot.
What it does not yet show
The operator's own account and counterfactual; it does not report staffing changes.
What you can check
Open Verizon's "Architecting autonomy" article of Jun 24, 2026 and find "over 70 million network configuration changes autonomously".
Does it change the assessment?
No. The impact index is never moved by a single event. Nor did this record change a layer: all 2 linked judgements above already rested on earlier evidence. This one adds to them.
Source
Verizon — Architecting autonomy (Verizon News, published Jun 24, 2026, by Yago Tenorio, chief technology officer) · 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