United States SMS and MMS Carrier Maintenance - T-Mobile
<p>The T-Mobile network in the United States is conducting a planned maintenance from 15 November 2026 at 20:30 PST until 16 November 2026 at 00:30 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.</p>
The latest update from Twilio.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Twilio
<p>The T-Mobile network in the United States is conducting a planned maintenance from 15 November 2026 at 20:30 PST until 16 November 2026 at 00:30 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.</p>
Affected components
8Twilio in the last 90 days
Full historyIncidents in 90 days
131
Days with an incident
49
Median duration
6 h 18 min
This incident
Not comparable
Other Twilio incidents
All incidentsTwilio·SMS Delivery Delays from a Subset of Twilio Short Codes to Multiple Networks in India
Twilio reports SMS delivery delays from a subset of Twilio Short Codes to subscribers on multiple networks in India. The issue affects SMS and CARRIER NETWORK SMS in APAC. Twilio has identified the cause and is working to resolve the issue.
Twilio·Silent Network Authentication (SNA) Failure Increase and Gateway API (Lookup API) Failure Increase in United Kingdom
Twilio reported failures in Silent Network Authentication (SNA) and in Lookup API transactions in the United Kingdom. Twilio identified the cause and monitored recovery. Twilio resolved the incident after 5 hours and 11 minutes.
Twilio·SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Multiple Networks in India
Twilio SMS delivery receipts were delayed from a subset of Twilio Short Codes to subscribers on multiple networks in India. The incident affected SMS in APAC and the related carrier network. Twilio reports that the incident is resolved and lasted 48 minutes.
Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes to Multiple Networks in India
Twilio SMS delivery from a subset of Twilio Short Codes to multiple networks in India had delays. The SMS and carrier network components in APAC were affected. Twilio resolved the incident after 3 hours and 12 minutes.
Twilio·Elastic SIP Trunking Voice Call Issues
Twilio Elastic SIP Trunking Voice calls did not work correctly on Termination US1. Twilio reports that the issue is resolved after 28 minutes. The service operates normally.
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