• Home
  • About
  • Events Calendar
  • Blueprint Guidelines
  • Privacy Policy
  • Manage Email Delivery
  • NextGenInfra.io
No Result
View All Result
Converge Digest
Thursday, June 4, 2026
  • Home
  • About
  • Events Calendar
  • Blueprint Guidelines
  • Privacy Policy
  • Manage Email Delivery
  • NextGenInfra.io
No Result
View All Result
Converge Digest
No Result
View All Result

Home » Network configuration error blamed for AT&T wireless outage

Network configuration error blamed for AT&T wireless outage

July 23, 2024
in All
A A

The Federal Communications Commission (FCC) has issued a comprehensive report detailing the causes and impacts of a nationwide AT&T wireless service outage on February 22, 2024. The outage, which lasted over 12 hours, prevented customers from using voice and data services, blocking more than 92 million phone calls and over 25,000 attempts to reach 911. The report also includes recommendations to prevent similar incidents in the future.

FCC Chairwoman Jessica Rosenworcel emphasized the gravity of the situation, stating, “When you sign up for wireless service, you expect it to be available when you need it – especially for emergencies.” The outage not only disrupted consumer communications but also affected public safety personnel using FirstNet. The FCC’s Public Safety and Homeland Security Bureau promptly launched an investigation, revealing several key findings about the outage’s extensive impact and the subsequent corrective actions taken by AT&T.

The outage affected users in all 50 states, Washington, D.C., Puerto Rico, and the U.S. Virgin Islands, impacting over 125 million devices. During the critical early hours of the outage, all 4G voice and 5G data services were unavailable to AT&T customers, including FirstNet subscribers. This disruption particularly impacted FirstNet, as device registrations approached normal only after the restoration of the dedicated network elements connected to AT&T’s broader network.

The FCC report highlights the technical cause of the outage, pinpointing two key steps that led to the network configuration error. An incorrect configuration was first made by an AT&T employee, followed by another employee loading this erroneous network change. This sequence revealed insufficient oversight and controls within AT&T’s processes, allowing the misconfiguration to propagate. Additionally, the network’s inability to handle the sudden influx of re-registration requests once the error was corrected prolonged the outage significantly.

Key Points:

  • The outage blocked over 92 million voice calls and prevented more than 25,000 calls to 911.
  • AT&T prioritized restoring FirstNet services but delayed notifying FirstNet users about the outage.
  • The outage was caused by a network configuration error due to insufficient oversight and controls.
  • The downstream network element lacked controls to mitigate the error, triggering Protection Mode and disconnecting all users.
  • System limitations caused registration congestion, prolonging the outage even after the initial error was corrected.
  • AT&T has since implemented additional technical controls, forensic work, and peer review procedures to prevent similar issues.

Corrective Actions by AT&T:

  • Implemented additional technical controls within 48 hours of the outage.
  • Scanned and updated network elements to prevent similar errors.
  • Enhanced network robustness and resilience through ongoing forensic work.
  • Adopted new procedures ensuring maintenance work requires completed peer reviews. Improved registration systems to handle higher capacity and quicker recovery from Protection Mode.

The full FCC report can be accessed here . .

Source: FCC
Tags: ATTFCC
ShareTweetShareSummarizeSummarize
Previous Post

Samsung Electro-Mechanics partners with AMD for substrates

Next Post

Dell’Oro: Front End Networks and Data Center Switch Sales

Jim Carroll

Jim Carroll

Editor and Publisher, Converge! Network Digest, Optical Networks Daily - Covering the full stack of network convergence from Silicon Valley

Related Posts

5G / 6G / Wi-Fi

Verizon Wins FCC Approval for Major Array Spectrum Acquisition

May 15, 2026
Legal / Regulatory

FCC Exempts Nokia Wi-Fi 8 Router, Elevon UAS

May 15, 2026
Legal / Regulatory

FCC Clears EchoStar Spectrum Sales to AT&T and SpaceX

May 12, 2026
Clouds and Carriers

AT&T Q1 Highlights Fiber Expansion, AI-Ready Network Strategy, OneConnect Push

April 22, 2026
Space

New FCC Framework Shifts Satellite Spectrum Policy to Performance-Based Model

April 11, 2026
Legal / Regulatory

FCC Votes to Expand 6 GHz Unlicensed Access 

January 29, 2026
Next Post

Verizon Maintains Course in Q2, Reports Significant Reduction in Capital Spending

Categories

  • 5G / 6G / Wi-Fi
  • AI Infrastructure
  • All
  • Automotive Networking
  • Blueprints
  • Clouds and Carriers
  • Data Centers
  • Enterprise
  • Explainer
  • Feature
  • Financials
  • Last Mile / Middle Mile
  • Legal / Regulatory
  • Optical
  • Quantum
  • Research
  • Security
  • Semiconductors
  • Space
  • Start-ups
  • Subsea
  • Sustainability
  • Video
  • Webinars

Archives

Tags

5G All AT&T Australia AWS Blueprint columns BroadbandWireless Broadcom China Ciena Cisco Data Centers Dell'Oro Ericsson FCC Financial Financials Huawei Infinera Intel Japan Juniper Last Mile Last Mille LTE Mergers and Acquisitions Mobile NFV Nokia Optical Packet Systems PacketVoice People Regulatory Satellite SDN Service Providers Silicon Silicon Valley StandardsWatch Storage TTP UK Verizon Wi-Fi
Converge Digest

A private dossier for networking and telecoms

Follow Us

  • Home
  • About
  • Events Calendar
  • Blueprint Guidelines
  • Privacy Policy
  • Manage Email Delivery
  • NextGenInfra.io

© 2026 Converge Digest - A private dossier for networking and telecoms.

No Result
View All Result
  • Home
  • About
  • Events Calendar
  • Blueprint Guidelines
  • Privacy Policy
  • Manage Email Delivery
  • NextGenInfra.io

© 2026 Converge Digest - A private dossier for networking and telecoms.

This website uses cookies. By continuing to use this website you are giving consent to cookies being used. Visit our Privacy and Cookie Policy.
Go to mobile version