outages.live
Live
TwilioMaintenance ·

United States SMS and MMS Carrier Maintenance - T-Mobile

MaintenanceOfficial update

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 UTC

As posted by Twilio

Scheduled

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

8
SMS Long Code, North AmericaMMS Long Code, North AmericaSMS Short Code, North AmericaMMS Short Code, North AmericaCARRIER NETWORK - SMS Long Code, North AmericaCARRIER NETWORK - MMS Long Code, North AmericaCARRIER NETWORK - SMS Short Code, North AmericaCARRIER NETWORK - MMS Short Code, North America

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

70

Days with an incident

39

Median duration

7 h 20 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

33 days
median 7 h 20 min
90 days agoToday

Other Twilio incidents

All incidents

Twilio·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Carriers in United States

Twilio MMS delivery receipts are delayed from a subset of Twilio Long Codes to subscribers on multiple Small Carriers in the United States. The affected components are MMS Long Code, CARRIER NETWORK MMS Long Code, and ZIPWHIP MESSAGING MMS Long Code in North America. Twilio identified the cause and is working to resolve the issue.

Degraded

Twilio·MMS Delivery Delays from a Subset of Twilio Long Codes and Short Codes to AT&T United States

Twilio reports MMS delivery delays from a subset of Twilio Long Codes and Short Codes to AT&T subscribers in the United States. The affected components include MMS Long Code and MMS Short Code in North America. Twilio has identified the cause and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed.

Degraded

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.

Resolved

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 subscribers in Brazil. The SMS and Carrier Network SMS services in Latin America were degraded. The incident is resolved and lasted about 14 hours and 47 minutes.

Resolved

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. Delivery receipts were delayed. Twilio reports that the incident is resolved. The incident lasted about 16 hours and 15 minutes.

Resolved

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.

Prompt
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.cc/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.

RSS
https://outages.cc/feed.xml?providers=twilio
Slack
/feed subscribe https://outages.cc/feed.xml?providers=twilio

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane