Live

US SMS and MMS Carrier Maintenance - Small US Carriers

MaintenanceOfficial update

A subset of small networks in the US are conducting a planned maintenance from 12 November 2026 at 20:00 PST until 12 November 2026 at 22:00 PST. During the maintenance window, there could be intermittent delays delivering SMS and MMS to small US carriers handsets.

The latest update from Twilio.

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Twilio

Scheduled

A subset of small networks in the US are conducting a planned maintenance from 12 November 2026 at 20:00 PST until 12 November 2026 at 22:00 PST. During the maintenance window, there could be intermittent delays delivering SMS and MMS to small US carriers handsets.

Affected components

16
SMS Long Code, North AmericaMMS Long Code, North AmericaSMS Short Code, North AmericaSMS Toll-Free, North AmericaMMS Short Code, North AmericaMMS Toll-Free, North AmericaCARRIER NETWORK - SMS Long Code, North AmericaCARRIER NETWORK - MMS Long Code, North America

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

83

Days with an incident

42

Median duration

7 h 17 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 17 min
90 days agoToday

Other Twilio incidents

All incidents

Twilio·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.

Resolved

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.

Resolved

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.

Resolved

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.

Degraded

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.

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