United States MMS Carrier Partner Maintenance
<p>Our MMS carrier partner in the United States is conducting a planned maintenance from 03 December 2026 at 01:00 PST until 03 December 2026 at 02:00 PST. During the maintenance window, there could be intermittent delays delivering MMS to T-Mobile United States, AT&T United States and Verizon United States handsets via United States 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>Our MMS carrier partner in the United States is conducting a planned maintenance from 03 December 2026 at 01:00 PST until 03 December 2026 at 02:00 PST. During the maintenance window, there could be intermittent delays delivering MMS to T-Mobile United States, AT&T United States and Verizon United States handsets via United States short codes.</p>
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
133
Days with an incident
49
Median duration
6 h 18 min
This incident
Not comparable
Other Twilio incidents
All incidentsTwilio·SMS Delivery Delays from Twilio to Brisanet Brazil
Twilio SMS delivery delays affect messages to Brisanet network subscribers in Brazil. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio has identified the cause and is working to resolve the issue.
Twilio·Voice Call Failures from a Subset of Twilio Phone Numbers to Colombia, Mexico, Chile, and Costa Rica
Twilio reports voice call failures from some Twilio phone numbers to network subscribers in Colombia, Mexico, Chile, and Costa Rica. The Voice, Latin America and carrier network voice components are degraded. Twilio identified the cause and continues to work on the fix.
Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes to Multiple Networks in India
SMS delivery delays affect a subset of Twilio Short Codes to subscribers on multiple networks in India. The SMS and carrier network components in APAC are degraded. Twilio reports a recovery and monitors service stability.
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.
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