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

Sean Harlow sean at seanharlow.info
Thu Feb 22 12:48:26 EST 2024


Another plausible explanation beyond Andy's suggestion of users having
trouble calling AT&T numbers and blaming their own carrier would be users
who are out of their primary carrier's coverage area and are unknowingly
roaming on to AT&T's infrastructure.  That would fit with how it seems like
reports of issues with other carriers are more sporadic than those on AT&T
or their MVNOs.

That's just a guess from an outsider though, I have no idea how common
roaming is these days or whose customers can roam where.

On Thu, Feb 22, 2024 at 12:03 PM Chapman, Brad (NBCUniversal) via
Outages-discussion <outages-discussion at outages.org> wrote:

> 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> wrote:
> >
> > 
> >
> >> On Feb 22, 2024, at 10:41 AM, Chapman, Brad (NBCUniversal) via
> Outages-discussion <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$
> "
> >>
> >> 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
> >
> 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
> https://puck.nether.net/mailman/listinfo/outages-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages-discussion/attachments/20240222/b3498306/attachment.htm>


More information about the Outages-discussion mailing list