United States SMS Carrier Partner Maintenance
Our SMS carrier partner in the United States is conducting a planned maintenance from 10 November 2026 at 23:00 PST until 11 November 2026 at 03:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to and from handsets via subset of United States short 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 carrier partner in the United States is conducting a planned maintenance from 10 November 2026 at 23:00 PST until 11 November 2026 at 03:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to and from handsets via subset of United States short codes.
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
75
Days with an incident
40
Median duration
7 h 20 min
This incident
Not comparable
Other Twilio incidents
All incidentsTwilio·Search Delays on Enterprise Knowledge
Twilio reports slow search and content ingestion on Enterprise Knowledge, including its use with Conversation Intelligence. Twilio says the service now operates normally and continues to monitor for stability.
Twilio·Delayed Email Validation History
Twilio reports delays in Email Validation history and statistics in the SendGrid UI. The affected components are Logs and TWILIO EMAIL - Logs. Mail send is not impacted. Twilio resolved the incident on 4 November 2026. The incident lasted about 2 hours and 48 minutes.
Twilio·SMS Delivery Delays from Twilio to Claro Brazil
SMS delivery to Claro network subscribers in Brazil had delays. The Twilio SMS and carrier network components in Latin America were affected. Twilio reports that the incident is resolved. The incident lasted about 4 hours and 44 minutes.
Twilio·SMS Delivery Delays from Twilio to Algar Telecom Brazil
Twilio SMS delivery delays affect messages to Algar Telecom network subscribers in Brazil. Twilio resolved the incident. The outage lasted about 5 hours and 20 minutes.
Twilio·MMS Delivery Failures from a Subset of Twilio Long Codes to GCI United States
Twilio MMS delivery failures affected a subset of Twilio Long Codes to GCI network subscribers in the United States. The components were MMS Long Code, North America and related carrier and ZIPWHIP messaging services. Twilio reports that the incident is resolved. It lasted about 32 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.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