Skip to main content

This year’s big AT&T outage was worse than we thought

An at&t office building.
Joshua Brown / Pexels

Back on February 22 this year, AT&T suffered a massive outage after a botched network update. Now, months later, the full scale of the outage has been revealed — and it’s much bigger than we thought at the time.

“All voice and 5G data services for AT&T wireless customers were unavailable, affecting more than 125 million devices, blocking more than 92 million voice calls, and preventing more than 25,000 calls to 911 call centers,” the Federal Communications Commission (FCC) said in its report.

The 911 failures are the biggest problem here for reasons that are easy to understand. There’s nothing worse than trying to reach 911 in an emergency and being unable to get through. The FCC report does show that AT&T attempted to restore FirstNet (First Responder Network Authority) first before residential and commercial AT&T users, which sounds like the correct way to go about it.

Down Detector website showing an outage map for AT&T on February 22, 2024.
Down Detector’s map of the February 22 outage. Down Detector

However, the FCC also criticized AT&T for several failures on top of failing to test the implementation of the network change. The FCC pointed to a lack of oversight and controls to ensure test that processes were followed or that the processes themselves were insufficient. AT&T was also unprepared for the congestion caused by user devices attempting to reconnect to the network at the same time. AT&T’s network was insufficiently robust to mitigate the congestion.

The outage affected all 50 states and territories, including Washington, D.C., Puerto Rico, and the U.S. Virgin Islands. The FCC criticized AT&T in the report for not following best practices, which require all network changes to be thoroughly tested, reviewed, and approved before implementation. The outage took over 12 hours for AT&T to resolve and fully restore service.

If this sounds a little familiar, it’s because it’s very similar to the Crowdstrike outage, which took out Microsoft devices globally last week and also involved the rolling out of an untested update with faulty code that broke everything. It’s also rather familiar because Verizon suffered a similar outage with a flawed update file in December 2022, something that earned it a penalty from the FCC and subjected it to a consent decree.

To AT&T’s credit, the carrier at least acknowledged responsibility for the outage and provided impacted customers with a $5 credit, which likely didn’t even cover a fraction of most people’s phone bills. On the plus side, the consequences from the FCC are likely to be more severe, with the Public Safety and Homeland Security bureau referring the matter to the FCC Enforcement Bureau to investigate a potential violation of FCC rules.

A Blue Screen of Death on a television monitor at LaGuardia Airport in New York City.
A malfunctioning monitor at New York’s LaGuardia Airport during the Crowdstrike outage Phil Nickinson / Digital Trend

If found responsible, AT&T could be made to pay a more significant fine and be subject to implementing a compliance plan, just like Verizon did last month when it had to pay a $1.05 million fine for its outage in December 2022. In terms of fixes, within two days of the outage, AT&T implemented new technical controls.

“This included scanning the network for any network elements lacking the controls that would have prevented the outage, and promptly putting those controls in place. AT&T has engaged in ongoing forensic work and implemented additional enhancements to promote network robustness and resilience,” the FCC said. The company also “implemented additional steps for peer review and adopted procedures to ensure that maintenance work cannot take place without confirmation that required peer reviews have been completed.”

This should help prevent future outages, at least for AT&T. However, it seems that the failures that lead to untested updates being pushed out are widespread across the industry, so hopefully, this will serve as a wake-up call for companies.

Ajay Kumar
Freelance Writer, Mobile
Ajay has worked in tech journalism for more than a decade as a reporter, analyst, and editor.
The T-Mobile Tuesdays app is about to get a big upgrade
A screenshot of the T-Mobile Tuesdays app, showing a promo for the new T Life app.

T-Mobile is a consistent leader in the ongoing 5G race, and to kick off 2024 on an interesting note, the carrier has announced that a big change is coming to its T-Mobile Tuesdays app. In short, the app is going away — and in its place, a new one is launching soon.

If you open the T-Mobile Tuesdays app today, January 2, you'll see a card that says "Introducing T Life." Below that is additional text that describes T Life as "a new app for T-Mobile Tuesdays."

Read more
The iPhone’s new Journal app is worse than I thought
Apple Journal app on an iPhone 15 Pro.

One of Apple’s recent focuses on iOS and watchOS is mental health and wellness. In the most recent watchOS 10 and iOS 17 updates, Apple added Mindfulness capture, which lets you log your mood for the day or how you feel at a particular moment. Similarly, it also launched a new Journal app.

Though Apple announced the Journal app in June’s WWDC23 keynote, Journal was absent from the initial iOS 17 release. With iOS 17.2, Apple finally released Journal to the public as another tool for better mental health and wellbeing.

Read more
Google Pixel Watch 2 may launch a lot sooner than we thought
Google Assistant listening on the Google Pixel Watch.

We're expecting a lot of Google Pixel hardware in 2023, and according to one new report, one of Google's upcoming releases this year is the Pixel Watch 2.

A report from 9to5Google on May 5 cites a "source" that claims the Google Pixel Watch 2 will be released later this fall alongside the Google Pixel 8 and Pixel 8 Pro. Given Google's past Pixel smartphone releases, that means we'll likely see the Pixel Watch 2 and Pixel 8 series debut in early October.
We could see the Pixel Watch 2 next week

Read more