[Outages-discussion] [EXTERNAL] Re: It wasn't just AT&T; every carrier was impacted. Why?

[Luke Wurl]

My own experience and reporting this morning seems to indicate issues were isolated to AT&T and its MVNOs only, and I agree with Andy’s assessment wholly.

Our Verizon & T-Mobile users haven’t been reporting any issues into our teams.


Luke A. Wurl  CCNP Enterprise
Vice President | Senior Network Architect and Telecom Manager
115 N. Neil St.
Champaign, IL  61820
P: 217.365.4908
C: 618.267.9261
F: 1.217.974.7302
From: Outages-discussion <outages-discussion-bounces at outages.org> On Behalf Of Chapman, Brad (NBCUniversal) via Outages-discussion
Sent: Thursday, February 22, 2024 11:03 AM
To: Outages Discussion <outages-discussion at outages.org>
Subject: Re: [Outages-discussion] [EXTERNAL] Re: It wasn't just AT&T; every carrier was impacted. Why?

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

I'm sorry, Andy. I must have emailed the outages-condescension listserv in error. My apologies.

Does anyone else have an insight about why the outage affected every one? Was AT&T's infrastructure really the source of the disruption as Andy says? If so, does this highlight a potential problem of a private company having too much control over a critical piece of public infrastructure?

...or did the equipment upgrade at the 33 Thomas Street NSA listening outpost not go as planned? :-D

—Sent from my iPhone

> On Feb 22, 2024, at 8:53 AM, Andy Ringsmuth via Outages-discussion <outages-discussion at outages.org<mailto:outages-discussion at outages.org>> wrote:
>
> 
>
>> On Feb 22, 2024, at 10:41 AM, Chapman, Brad (NBCUniversal) via Outages-discussion <outages-discussion at outages.org<mailto:outages-discussion at outages.org>> wrote:
>>
>> Take a look at this scrolling screenshot the reports from Downdetector: every major carrier had some issue, with reports spiking around the same time.
>>
>> Link: "https://urldefense.com/v3/__https://imgur.com/gallery/O3sm3qy__;!!PIZeeW5wscynRQ!rv688OpWswUnLFdugjEzHYHhrlS2Omb0viPzs_V1eR15-dTlj2DMBGFbdnd9ZCzHvQWXZ5eTLtMUv_BAOi6YvfTmRfRxltw$<https://urldefense.com/v3/__https://imgur.com/gallery/O3sm3qy__;!!PIZeeW5wscynRQ!rv688OpWswUnLFdugjEzHYHhrlS2Omb0viPzs_V1eR15-dTlj2DMBGFbdnd9ZCzHvQWXZ5eTLtMUv_BAOi6YvfTmRfRxltw$> "
>>
>> Someone commented on this post already about a "SIM Card database issue."
>>
>> Is that a credible explanation? If so, how and why?
>>
>> -Brad
>
> DownDetector is mostly garbage. It consists of 100% user-submitted reports.
>
> But the tech illiterate media has no clue, so they take it as gospel and run with it.
>
> If you are a T-Mobile customer and calling your girlfriend or boss or whomever and they are an AT&T customer, and it doesn’t go through, who do you blame? T-Mobile of course. Even though they were not at fault.
>
> Also, how many of those MVNOs actually use AT&T’s infrastructure? Quite a few.
>
> That’s what is going on with the other reports on DownDetector.
>
> Again, repeat after me: DownDetector is not an official source. DownDetector is not an official source. DownDetector is not an official source.
>
>
> -Andy
> _______________________________________________
> Outages-discussion mailing list
> Outages-discussion at outages.org<mailto:Outages-discussion at outages.org>
> https://urldefense.com/v3/__https://puck.nether.net/mailman/listinfo/outages-discussion__;!!PIZeeW5wscynRQ!rv688OpWswUnLFdugjEzHYHhrlS2Omb0viPzs_V1eR15-dTlj2DMBGFbdnd9ZCzHvQWXZ5eTLtMUv_BAOi6YvfTmkifKiYo$<https://urldefense.com/v3/__https://puck.nether.net/mailman/listinfo/outages-discussion__;!!PIZeeW5wscynRQ!rv688OpWswUnLFdugjEzHYHhrlS2Omb0viPzs_V1eR15-dTlj2DMBGFbdnd9ZCzHvQWXZ5eTLtMUv_BAOi6YvfTmkifKiYo$>
_______________________________________________
Outages-discussion mailing list
Outages-discussion at outages.org<mailto:Outages-discussion at outages.org>
https://puck.nether.net/mailman/listinfo/outages-discussion<https://puck.nether.net/mailman/listinfo/outages-discussion>  

The information contained in this e-mail is privileged and confidential.  Unless otherwise indicated or obvious from the message, this is intended only for the individual(s) listed above.  Please see our Privacy Notices at http://www.busey.com. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages-discussion/attachments/20240222/acd719df/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image689784.jpg
Type: image/jpeg
Size: 4982 bytes
Desc: image689784.jpg
URL: <https://puck.nether.net/pipermail/outages-discussion/attachments/20240222/acd719df/attachment-0001.jpg>