T-Mobile has acknowledged the outage and attributed it to a fiber cut: https://twitter.com/NevilleRay/status/1625355891301285888 Neville twitter.com
> On Feb 14, 2023, at 1:02 AM, Nate via Outages <[email protected]> wrote: > > It's more looking like an edge router, or core switch failed from all the > research I have done so far. > > Checked AWS - UP > Checked Azure - UP > Checked Zayo - UP > Checked Other Backhauls - UP > > If it was chatter, most likely would only have taken down the network in that > area. This was a multi state outage. > > Or it could be human error and someone deleted the BGP Routes, or someone > went "Oh look a loose network cable that isn't plugged into anything *click > into the same switch as it's already plugged into*" 🙄 > > Either way, it appears to be "Stable" as of now, haven't seen a bounce since > about 45 minutes ago. > > > > > On Mon, Feb 13, 2023, 8:51 PM Dennis Boone via Outages <[email protected] > <mailto:[email protected]>> wrote: >> > I'm not one to refer to Downdetector often, but in this case it's >> > interesting that pretty much every mobile carrier in the US took a >> > hit at the same time. However, the same is true for Apple support, >> > Google, Samsung, American Express, and a handful of others. Feels >> > sorta cloud-ish. >> >> There's an ongoing active shooter event on campus at Michigan State >> University. The start of the spike on the down detector graphs could >> correspond to that. Seems it might be possible that the chatter >> surrounding this event may be related. >> >> De >> _______________________________________________ >> Outages mailing list >> [email protected] <mailto:[email protected]> >> https://puck.nether.net/mailman/listinfo/outages > _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
