AT&T believes the February 22 outage “was caused by the application and execution of an incorrect process as we were expanding our network, not a cyber attack”
Context & Ripple Effects
AT&T attributed the disruption to an incorrect process used during network expansion rather than an intrusion. That places the incident alongside an earlier AT&T cellular outage tied to its landline network, where dependencies outside the radio network also disrupted service.
The distinction matters because a later FCC investigation into the February outage quantified its impact on voice calls and 911 attempts, raising the operational stakes of change controls even when a cyberattack is ruled out.
First-order effects
- AT&T can focus its immediate investigation and remediation on the expansion workflow, execution safeguards, and rollback procedures rather than treating the event as a confirmed cyber incident.
- Customers and emergency callers experienced a service failure whose stated cause was internal operational change, making restoration and accountability chiefly a network-operations issue.
Second-order effects
- AT&T’s peers face renewed pressure to test change-management and failover processes across interconnected network layers; T-Mobile's third-party circuit failure and IP traffic storm illustrates how quickly a localized dependency can become a broad outage.
- The episode separates cyber-resilience planning from availability engineering, while showing that both require clear incident communications when the initial cause is uncertain.
Third-order effects
- If network expansion continues to add operational complexity, carrier reliability will increasingly depend on automated guardrails, staged deployment, and rollback discipline—not only on physical coverage investment.
- Major outages may draw more scrutiny of how carriers protect emergency access during routine network changes, particularly where internal processes can create nationwide-scale effects.
The trend: Telecom reliability is becoming a software-and-process governance challenge as network expansion makes configuration and execution errors as consequential as infrastructure failures.