Multiple Destination SMS and MMS Carrier Partner Maintenance
Our SMS and MMS carrier partner in the United States and Canada is conducting a planned maintenance from 12 November 2026 at 20:00 PST until 13 November 2026 at 03:00 PST. During the maintenance window, there could be intermittent delays delivering SMS and MMS to and from handsets via subset of United States and Canada long codes.
The latest update from Twilio.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Twilio
Our SMS and MMS carrier partner in the United States and Canada is conducting a planned maintenance from 12 November 2026 at 20:00 PST until 13 November 2026 at 03:00 PST. During the maintenance window, there could be intermittent delays delivering SMS and MMS to and from handsets via subset of United States and Canada long codes.
Affected components
4Twilio in the last 90 days
Full historyIncidents in 90 days
83
Days with an incident
42
Median duration
7 h 17 min
This incident
Not comparable
Other Twilio incidents
All incidentsTwilio·Notification Delivery Logs Unavailable in Console
Twilio notification delivery logs were unavailable in Console for Conversations and Programmable Messaging Conversations. Twilio reports that the issue is resolved. The outage lasted about 7 minutes.
Twilio·Notification Logs Unavailable in Console
Twilio notification delivery logs did not populate new data in the Console. The problem affected the Notify component. Twilio reports that the issue is resolved. The outage lasted about 95 minutes.
Twilio·SMS Delivery Delays between Twilio and T-Mobile in Czech Republic
SMS delivery delays affect Twilio and T-Mobile subscribers in the Czech Republic. Twilio reports that the incident is resolved. The outage lasted about 9 hours.
Twilio·Voice Call Silent and One-Way Audio Between a Subset of Twilio Phone Numbers and Colombia
Voice calls have silent audio or one-way audio between some Twilio phone numbers and Colombia. The Latin America Voice component and the carrier network in Latin America are affected. Twilio identified the cause and is working to resolve the issue.
Twilio·SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Liberty Puerto Rico
SMS delivery receipts from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico had delays. The incident is resolved and the service operates normally. The incident lasted about 16 hours.
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.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.
https://outages.cc/feed.xml?providers=twilio/feed subscribe https://outages.cc/feed.xml?providers=twilioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane