AT&T Long Distance Network Collapse
A single line of buggy C code in a 4ESS switch patch caused a cascading SS7 recovery storm on January 15, 1990, dropping roughly 60 million calls over nine hours.
02Deep-Dive Technical Analysis
The patch handled a data-structure flag without an accompanying lock during fault recovery. When one 4ESS reset, it sent SS7 restore messages that crashed neighboring switches in a repeating ~7-second cascade until all 114 switches in the long-distance mesh were down. Because SS7 recovery messages propagated the fault, the signaling network designed for resilience became the delivery mechanism for the outage.
03Vulnerability & Exploit Flow
Cascading state machine crash loop.
04Recommended Defense & Mitigation Protocol
Fault-tolerant message queues and circuit breaker fault domains.
05Security Impact & Geopolitical Consequence
Proved the fragility of monolithic signaling control planes and became the canonical case study in cascading failure, still cited in BGP route-leak and cloud control-plane post-mortems.
06Authoritative Standards & External References
- 01Cal Poly — All Circuits are Busy Now: The 1990 AT&T Long Distance Network Collapse
- 02TU München (Thomas Huckle) — Application Note: AT&T Phone Crash
- 03RISKS Digest Vol. 9 Issue 62 — Cause of AT&T network failure
- 04Project Gutenberg (Bruce Sterling) — The Hacker Crackdown, Part One: Crashing the System
07Related Topic Cluster Records
Master 5G Core, SS7 Defense & Subsea Cable Auditing
Ready to turn your historical knowledge into certified hands-on expertise? Register free on TelcoSec Academy to access interactive lab challenges, or consult our enterprise team for carrier-grade signaling assessments and portable BTS hardware.