MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Networks in United States
Twilio MMS delivery is delayed from a subset of Twilio Long Codes to subscribers on multiple United States networks. This affects MMS Long Code in North America, the related carrier network, and Zipwhip Messaging. Twilio has identified the cause and is working to resolve the issue.
State
Identified
Started
Ongoing for
1 h 3 min
Worst impact
Degraded
Timeline
1 updateIdentified
1 h 3 min 100%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing MMS delivery delays from a subset of Twilio Long Codes to network subscribers on multiple networks in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
111
Days with an incident
47
Median duration
7 h 17 min
This incident
85% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Failures from a Subset of Twilio Phone Numbers to K-Cell Kazakhstan
SMS delivery failures affect a subset of Twilio phone numbers that send to K-Cell subscribers in Kazakhstan. The affected components are SMS, APAC and CARRIER NETWORK - SMS, APAC. Twilio has identified the cause and works to resolve the issue.
Twilio·Voice Call Failures in JP1
Twilio reports that Voice services in JP1 do not work. Calls can fail when users make or receive calls with the Voice JavaScript SDK. The components Client Web AU1 and PROGRAMMABLE VOICE AU1 - Client Web AU1 are affected. Twilio reports that the service operates normally again, and Twilio continues to monitor it. The incident is not resolved.
Twilio·On Call Engineers are Investigating
Twilio reported a problem with JS client connectivity to the Tokyo edge. Twilio investigated the issue. The issue is now resolved, and it lasted 19 minutes.
Twilio·SMS Delivery Failures from Twilio to Turkcell Turkey
Twilio SMS delivery to Turkcell network subscribers in Turkey failed. This affected SMS in Europe and the Carrier Network for SMS in Europe. Twilio reports that the incident is resolved. The outage lasted about 3 hours and 55 minutes.
Twilio·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.
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