<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">T-Mobile has acknowledged the outage and attributed it to a fiber cut: <div><br></div><div><div style="display: block;"><div style="-webkit-user-select: all; -webkit-user-drag: element; display: inline-block;" class="apple-rich-link" draggable="true" role="link" data-url="https://twitter.com/NevilleRay/status/1625355891301285888"><a style="border-radius:10px;font-family:-apple-system, Helvetica, Arial, sans-serif;display:block;-webkit-user-select:none;width:300px;user-select:none;-webkit-user-modify:read-only;user-modify:read-only;overflow:hidden;text-decoration:none;" class="lp-rich-link" rel="nofollow" href="https://twitter.com/NevilleRay/status/1625355891301285888" dir="ltr" role="button" draggable="false" width="300"><table style="table-layout:fixed;border-collapse:collapse;width:300px;background-color:#EBF7FF;font-family:-apple-system, Helvetica, Arial, sans-serif;" class="lp-rich-link-emailBaseTable" cellpadding="0" cellspacing="0" border="0" width="300"><tbody><tr><td vertical-align="center"><div style="margin:10px 16px 0px 16px;color:#272727;font-weight:300;text-align:left;width:268px;font-size:11pt;word-wrap:break-word;overflow:hidden;" class="lp-rich-link-quotedText">Our teams are rapidly addressing a 3rd party fiber interruption issue that has intermittently impacted some voice, messaging and data services in several areas. The situation is improving and we hope to have a full resolution very soon. We apologize for any disruption caused.</div></td></tr><tr><td vertical-align="center"><table bgcolor="#EBF7FF" cellpadding="0" cellspacing="0" width="300" style="font-family:-apple-system, Helvetica, Arial, sans-serif;table-layout:fixed;background-color:rgba(235, 247, 255, 1);" class="lp-rich-link-captionBar"><tbody><tr><td style="padding:6px 0px 6px 16px;" class="lp-rich-link-captionBar-leftIconItem" width="25"><a rel="nofollow" href="https://twitter.com/NevilleRay/status/1625355891301285888" draggable="false"><img style="pointer-events:none !important;display:inline-block;width:25px;height:25px;border-radius:3px;" width="25" height="25" draggable="false" class="lp-rich-link-captionBar-leftIcon" alt="twitter.2.ico" src="cid:14668E4F-E113-42CF-9B40-662A47E4A0B0"></a></td><td style="padding:8px 0px 8px 0px;" class="lp-rich-link-captionBar-textStackItem"><div style="max-width:100%;margin:0px 16px 0px 10px;overflow:hidden;" class="lp-rich-link-captionBar-textStack"><div style="word-wrap:break-word;font-weight:500;font-size:12px;overflow:hidden;text-overflow:ellipsis;text-align:left;" class="lp-rich-link-captionBar-textStack-topCaption-leading"><a rel="nofollow" href="https://twitter.com/NevilleRay/status/1625355891301285888" style="text-decoration: none" draggable="false"><font color="#272727" style="color: rgba(0, 0, 0, 0.847059);">Neville</font></a></div><div style="word-wrap:break-word;font-weight:400;font-size:11px;overflow:hidden;text-overflow:ellipsis;text-align:left;" class="lp-rich-link-captionBar-textStack-bottomCaption-leading"><a rel="nofollow" href="https://twitter.com/NevilleRay/status/1625355891301285888" style="text-decoration: none" draggable="false"><font color="#808080" style="color: rgba(0, 0, 0, 0.498039);">twitter.com</font></a></div></div></td></tr></tbody></table></td></tr></tbody></table></a></div></div><br><div><br><blockquote type="cite"><div>On Feb 14, 2023, at 1:02 AM, Nate via Outages <outages@outages.org> wrote:</div><br class="Apple-interchange-newline"><div><div dir="auto">It's more looking like an edge router, or core switch failed from all the research I have done so far.<div dir="auto"><br></div><div dir="auto">Checked AWS - UP</div><div dir="auto">Checked Azure - UP</div><div dir="auto">Checked Zayo - UP</div><div dir="auto">Checked Other Backhauls - UP</div><div dir="auto"><br></div><div dir="auto">If it was chatter, most likely would only have taken down the network in that area. This was a multi state outage. </div><div dir="auto"><br></div><div dir="auto">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*" 🙄 </div><div dir="auto"><br></div><div dir="auto">Either way, it appears to be "Stable" as of now, haven't seen a bounce since about 45 minutes ago.</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Feb 13, 2023, 8:51 PM Dennis Boone via Outages <<a href="mailto:outages@outages.org">outages@outages.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> > I'm not one to refer to Downdetector often, but in this case it's<br>
> interesting that pretty much every mobile carrier in the US took a<br>
> hit at the same time. However, the same is true for Apple support,<br>
> Google, Samsung, American Express, and a handful of others. Feels<br>
> sorta cloud-ish.<br>
<br>
There's an ongoing active shooter event on campus at Michigan State<br>
University. The start of the spike on the down detector graphs could<br>
correspond to that. Seems it might be possible that the chatter<br>
surrounding this event may be related.<br>
<br>
De<br>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org" target="_blank" rel="noreferrer">Outages@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
</blockquote></div>
_______________________________________________<br>Outages mailing list<br>Outages@outages.org<br>https://puck.nether.net/mailman/listinfo/outages<br></div></blockquote></div><br></div></body></html>