Posted on 02/23/2024 11:00:57 AM PST by plain talk
So Verizon, ATT, and T Mobil ALL had a software update at the same time REALLY??? I call BS!!
Damn’ right. Ain’t Texting & Talking eff’d up. Badly.
It must have been geographically determined. In my area Verizon and T mobile were fine. The problems came from AT & T users attempting to communicate with other carriers and vice-versa.
Software update with a DEI connection?
ID10T error.
Sounds like the government. Whenever our IT systems in the Air Force were updated, there were ALWAYS problems that they had to go back and fix.
Who believes this lie? No seriously, who. I need your names and bank draft numbers so I can sell you the Brooklyn Bridge. Cheap REALLY cheap!
No, but what else is AT&T going to say? The truth? Right, any evidence they might have has already disappeared.
But it sounded so much more alarming when it was a solar flair or espionage
And, some of them resell AT&T minutes.
And, AT&T owns discount sellers like Cricket.
I guess you would have to have network analyzer to figure out which network you were really talking through...
Correct.
It was a “special ATT solar flare….”
D’oh!
Oh yeah, sure! Coincidentally happened on the same day as a huge military exercise!
*********
What huge military exercise?
WFFM _ aka “whiff-fem”
Works
Fine
For
Me
AT&T failed to test disastrous update that kicked all devices off network
AT&T caused outage that blocked 92 million calls, 25,000 attempts to reach 911.
At 2:42 am CST on February 22, an AT&T “employee placed a new network element into its production network during a routine night maintenance window in order to expand network functionality and capacity,” the FCC said. The configuration “did not conform to AT&T’s established network element design and installment procedures, which require peer review.”
An adequate peer review should have prevented the network change from being approved and from being loaded onto the network, but this peer review did not take place, the FCC said. The configuration error was made by one employee, and the misconfigured network element was loaded onto the network by a second employee.
“The fact that the network change was loaded onto the AT&T Mobility network indicates that AT&T Mobility had insufficient oversight and controls in place to ensure that approval had occurred prior to loading,” the FCC said.
A government investigation has revealed more detail on the impact and causes of a recent AT&T outage that happened immediately after a botched network update. The nationwide outage on February 22, 2024, blocked over 92 million phone calls, including over 25,000 attempts to reach 911.
The FCC Public Safety and Homeland Security Bureau finds that the extensive scope and duration of this outage was the result of several factors, all attributable to AT&T Mobility, including a configuration error, a lack of adherence to AT&T Mobility’s internal procedures, a lack of peer review, a failure to adequately test after installation, inadequate laboratory testing, insufficient safeguards and controls to ensure approval of changes affecting the core network, a lack of controls to mitigate the effects of the outage once it began, and a variety of system issues that prolonged the outage once the configuration error had been remedied.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.