- Verizon, T-Mobile, and Sprint users across the US are being impacted by a network connectivity issue.
- Many users are saying they can’t make or receive calls.
- Other users are indicating that they’re unable to send or receive text messages.
Updated: Due to a network problem that was later revealed to be a routing issue, T-Mobile users across the United States are reporting that they’re unable to make or receive phone calls. The issue is also impacting a subset of Sprint users as well. Additionally, some users are indicating that they’ve been unable to send text messages. From what we can gather thus far, data doesn’t to be impacted to the same degree.
According to reports, most of the United States is being impacted by the somewhat bizarre outage. The areas hit hardest appear to be Texas, Southern California, and the tri-state area.
According to DownDetector, the problems started at around Noon and only intensified over the next few hours. With respect to T-Mobile specifically, DownDetector relays that 52% of reported issues involve no signal. 19% of reported issues, meanwhile, involve no mobile internet access.
While initial reports suggested that Verizon was also hit with an outage, that doesn’t appear to be the case. Speaking on the matter, a Verizon spokesperson provided us with the following statement:
We’re aware that another carrier is having network issues. Calls to and from that carrier may receive an error message.
Twitter users who called their respective carriers to see what the problem was were told that engineers are currently looking into the issue.
Our engineers are working to resolve a widespread routing issue affecting voice & text. Customers may experience longer care wait times. Please try third-party calling apps (FaceTime, WhatsApp, Signal) as a temp solution.
— T-Mobile Help (@TMobileHelp) June 15, 2020
T-Mobile CTO Neville Ray tweeted the following a short while ago:
Our engineers are working to resolve a voice and data issue that has been affecting customers around the country. We’re sorry for the inconvenience and hope to have this fixed shortly.
— Neville (@NevilleRay) June 15, 2020