United States SMS and MMS Carrier Maintenance - T-Mobile
The T-Mobile network in the United States is conducting a planned maintenance from 03 November 2026 at 20:00 PST until 04 November 2026 at 05:00 PST. During the maintenance window, there could be intermittent delays delivering SMS and MMS to T-Mobile United States handsets when sending via long codes and short codes. We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.
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 03 November 2026 at 20:00 PST until 04 November 2026 at 05:00 PST. During the maintenance window, there could be intermittent delays delivering SMS and MMS to T-Mobile United States handsets when sending via long codes and short codes. We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.
Affected components
8Twilio in the last 90 days
Full historyIncidents in 90 days
67
Days with an incident
39
Median duration
7 h 14 min
This incident
Not comparable
Other Twilio incidents
All incidentsTwilio·SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil
Twilio SMS delivery delays affect a subset of Twilio Short Codes and Long Codes to Brisanet network subscribers in Brazil. The SMS and Carrier Network SMS components in Latin America are degraded. Twilio identified the cause and is working to resolve the issue.
Twilio·MMS Delivery Receipt Delays from a Subset of Twilio Long Codes to GCI Communication United States
Twilio reports delays in MMS delivery receipts from some Twilio Long Codes to GCI Communication subscribers in the United States. This affects MMS Long Code, the carrier network, and ZIPWHIP MESSAGING in North America. Twilio identified the cause and is working to resolve the issue. Message delivery can still succeed.
Twilio·SMS Delivery Delays from Twilio to Entel Bolivia
Twilio SMS delivery to Entel network subscribers in Bolivia had delays. The incident affected SMS in Latin America and the carrier network for SMS in Latin America. Twilio reports that the incident is resolved and that the service operates normally. The incident lasted about 9 hours and 37 minutes.
Twilio·SMS Delivery Delays from Twilio to Lycamobile United Kingdom
Twilio SMS delivery to Lycamobile United Kingdom subscribers had delays. The affected components were SMS, Europe and Carrier Network SMS, Europe. Twilio reports that the incident is resolved, and the delays lasted about 160 minutes.
Twilio·Voice Call Audio Quality Degradation for Outbound Calls from Twilio to US Network Subscribers
Twilio voice calls from network subscribers to Twilio phone numbers have audio delays and high packet loss. The affected regions are North America, Latin America, APAC, Europe, and the Middle East and Africa. Twilio reports a recovery in these calls and monitors service stability.
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