United States and Canada Twilio SMS and MMS Maintenance
Twilio is 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 or failures delivering SMS and MMS to and from United States and Canada handsets when sending via subset of long codes.
The latest update from Twilio.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Twilio
Twilio is 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 or failures delivering SMS and MMS to and from United States and Canada handsets when sending via subset of long codes.
Affected components
6Twilio in the last 90 days
Full historyIncidents in 90 days
106
Days with an incident
47
Median duration
7 h 30 min
This incident
Not comparable
Other Twilio incidents
All incidentsTwilio·Retroactive Incident Impacting Twilio Usage APIs
Twilio Usage APIs were degraded for 6 minutes between 16:42pm and 16:48 Pacific Time on 11/10/2026. During this period of time customers may have experienced 5xx errors. The issue has now been resolved.
Twilio·Email Template Editor Issues
Twilio SendGrid Marketing Campaigns had degraded email template editing. HTML entities changed to spaces, links changed, and template content did not render correctly after save or preview. Twilio resolved the issue. The outage lasted 1 hour and 44 minutes.
Twilio·SMS Delivery Receipt Delays from Twilio Phone Numbers to Movistar Venezuela
Twilio SMS delivery receipts to Movistar network subscribers in Venezuela were delayed. This affected SMS in Latin America and the carrier network for SMS in Latin America. Twilio reports that the incident is resolved. The incident lasted about 3 hours and 26 minutes.
Twilio·Gateway API (Lookup API) Failure Increase on Verizon in United States
Twilio Lookup API transactions on Verizon in the United States failed. The affected components were Lookup SIM Swap, Legacy Identity MatchAndAttributes, and their carrier network parts. Twilio reports that the incident is resolved. It lasted 10 hours and 23 minutes.
Twilio·WhatsApp Business API Message Send Failures
Twilio reports that WhatsApp Business API message sends failed. The WhatsApp Messaging component was affected. Twilio reported error 63007 for outbound messages. Twilio identified a third-party provider dependency, mitigated the issue, and monitored the fix. The incident is resolved. It lasted about 16 hours and 29 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