SMS Delivery Delays from Twilio to MTS Kazakhstan
SMS delivery to MTS network subscribers in Kazakhstan shows delays. This affects the SMS and Carrier Network SMS components in APAC. Twilio reports the status as investigating.
State
Investigating
Started
Ongoing for
29 min
Worst impact
Degraded
Timeline
1 updateInvestigating
29 min 100%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing SMS delivery delays from Twilio to MTS network subscribers in Kazakhstan. Our team is actively investigating this 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
113
Days with an incident
47
Median duration
7 h 14 min
This incident
93% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Failures from a Subset of Twilio Phone Numbers to Tcell Tajikistan
SMS delivery failures affect a subset of Twilio phone numbers that send to Tcell subscribers in Tajikistan. The affected components are SMS, Middle East & Africa and the related carrier network. Twilio reports that the issue is under investigation.
Twilio·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Networks in United States
Twilio reports MMS delivery delays from a subset of Twilio Long Codes to subscribers on multiple networks in the United States. The affected components are MMS Long Code, North America and CARRIER NETWORK - MMS Long Code, North America. Twilio has identified the cause and is working to resolve the issue.
Twilio·SMS Delivery Failures from a Subset of Twilio Phone Numbers to K-Cell Kazakhstan
Twilio 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 reports a recovery in delivery and monitors service stability.
Twilio·Voice Call Failures in JP1
Twilio Voice services in JP1 had failures for calls with the Voice JavaScript SDK. The affected components were Client Web AU1 and PROGRAMMABLE VOICE AU1 - Client Web AU1. Twilio reports that the issue is resolved. The outage lasted about 3 hours and 51 minutes.
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.
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