United States SMS and MMS Carrier Maintenance - T-Mobile
The T-Mobile network in the United States is conducting a planned maintenance from 04 November 2026 at 20:00 PST until 11 November 2026 at 05:00 PST. During the maintenance window, there could be intermittent delays delivering SMS and MMS to and from T-Mobile United States handsets when sending via long codes and short codes.
The latest update from Twilio.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Twilio
The T-Mobile network in the United States is conducting a planned maintenance from 04 November 2026 at 20:00 PST until 11 November 2026 at 05:00 PST. During the maintenance window, there could be intermittent delays delivering SMS and MMS to and from T-Mobile United States handsets when sending via long codes and short codes.
Affected components
8Twilio in the last 90 days
Full historyIncidents in 90 days
70
Days with an incident
39
Median duration
7 h 20 min
This incident
Not comparable
Other Twilio incidents
All incidentsTwilio·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Carriers in United States
Twilio MMS delivery reports are delayed for a subset of Twilio Long Codes in North America. The delay affects messages to multiple small carriers in the United States. Twilio identified the cause and continues to work on a fix. Messages may still arrive, but delivery receipts may come late.
Twilio·MMS Delivery Delays from a Subset of Twilio Long Codes and Short Codes to AT&T United States
MMS delivery and delivery receipts do not work for some Twilio Long Codes and Short Codes that send to AT&T subscribers in the United States. Twilio identified the cause and is working to resolve the issue. Message delivery can still succeed, but delivery receipts can be delayed.
Twilio·MMS Delivery Delays and Failures from a Subset of Twilio Short Codes to T-Mobile and Verizon United States
MMS delivery delays and failures affected a subset of Twilio Short Codes to T-Mobile and Verizon subscribers in the United States. Twilio reports that the incident is resolved. The incident lasted about 6 hours and 18 minutes.
Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil
Twilio SMS delivery delays affected a subset of Short Codes and Long Codes to Brisanet network subscribers in Brazil. Twilio reported the incident as resolved after about 14 hours and 47 minutes.
Twilio·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Networks United States
MMS delivery from a subset of Twilio Long Codes to multiple small networks in the United States did not work. The incident is resolved. It lasted about 16 hours and 15 minutes.
Follow Twilio
Your coding agent knows when Twilio is down, and tells you when a failure is theirs, not yours. You can also get Twilio incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "twilio" and tell me if Twilio has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=twilio/feed subscribe https://outages.live/feed.xml?providers=twilioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane