SMS Delivery Delays from Twilio to Multiple Networks in India
Twilio SMS delivery to network subscribers on multiple networks in India had delays. The affected components were SMS, APAC and CARRIER NETWORK - SMS, APAC. Twilio reports that the incident is resolved. It lasted about 3 hours and 42 minutes.
State
Resolved
Started
Lasted
3 h 42 min
Worst impact
Degraded
Timeline
5 updatesInvestigating
36 min 16%
Identified
1 h 9 min 31%
Monitoring
1 h 57 min 53%
Updates
Times in UTCAs posted by Twilio
We have observed a recovery in SMS delivery from Twilio to network subscribers on multiple networks in India and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
Twilio customers may be experiencing SMS delivery delays from Twilio to network subscribers on multiple networks in India. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.
Twilio customers may be experiencing SMS delivery delays from Twilio to network subscribers on multiple networks in India. 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.
Twilio customers may be experiencing SMS delivery delays from Twilio to network subscribers on multiple networks in India. 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
91
Days with an incident
43
Median duration
6 h 53 min
This incident
46% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Receipt Delays from a Subset of Twilio Long Codes and Short Codes to Multiple Networks in United States
Twilio SMS delivery receipts are delayed for a subset of Long Codes and Short Codes to multiple networks in the United States. Some affected components are SMS Long Code, SMS Short Code, and ZIPWHIP MESSAGING. Twilio has identified the cause and is working to resolve the issue. Message delivery can succeed, but delivery receipts can be delayed.
Twilio·SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Multiple Networks in New Zealand
Twilio reports delays in SMS delivery receipts from a subset of Twilio Short Codes to multiple networks in New Zealand. The affected components are SMS, APAC and CARRIER NETWORK - SMS, APAC. Twilio has identified the cause and is working to resolve the issue; message delivery may succeed, but delivery receipts may be delayed.
Twilio·SMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Networks in Chile
Twilio reports SMS delivery delays from a subset of Twilio Long Codes to subscribers on multiple networks in Chile. The issue affects SMS in Latin America and the related carrier network. Twilio has identified the cause and is working to resolve the issue.
Twilio·SMS Delivery Delays from Twilio to Claro Dominican Republic
Twilio SMS delivery delays affected Claro network subscribers in the Dominican Republic. Twilio reported the incident as resolved. The incident lasted about 3 hours and 46 minutes.
Twilio·TwiML ConversationRelay Documents Page Error
The ConversationRelay documentation page on the Twilio docs site had an error. Links on that page sent users to a login prompt instead of other documentation pages. Twilio reported the issue as resolved after 116 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