SMS Delivery Delays from a Subset of Twilio Short Codes to Multiple Networks in India
SMS delivery delays affect a subset of Twilio Short Codes to network subscribers on multiple networks in India. The affected components are SMS, APAC and CARRIER NETWORK - SMS, APAC. Twilio reports a recovery and monitors service stability.
State
Monitoring
Started
Ongoing for
2 h 4 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
6 min 5%
Identified
1 h 49%
Monitoring
58 min 47%
Updates
Times in UTCAs posted by Twilio
We have observed a recovery in SMS delivery from a subset of Twilio Short Codes 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 a subset of Twilio Shortcode 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 a subset of Twilio Phone Numbers 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
129
Days with an incident
49
Median duration
6 h 25 min
This incident
68% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Multiple Networks in India
Twilio SMS delivery receipts were delayed from a subset of Twilio Short Codes to subscribers on multiple networks in India. The incident affected SMS in APAC and the related carrier network. Twilio reports that the incident is resolved and lasted 48 minutes.
Twilio·Elastic SIP Trunking Voice Call Issues
Twilio Elastic SIP Trunking Voice calls did not work correctly on Termination US1. Twilio reports that the issue is resolved after 28 minutes. The service operates normally.
Twilio·Voice Call Post Dial Delay from a Subset of Twilio Phone Numbers to United States
Twilio Voice and carrier network voice in North America had post dial delay on calls from some Twilio phone numbers to United States subscribers. Twilio identified the cause and resolved the incident. The outage lasted 30 minutes.
Twilio·SMS Delivery Receipt Failures from Twilio to Claro Costa Rica
Twilio reports SMS delivery receipt failures to Claro network subscribers in Costa Rica. These failures affect SMS and the carrier network in Latin America. Message delivery can succeed, but delivery receipts can fail. Twilio is investigating the problem.
Twilio·SMS Delivery Delays and Failures from Twilio to Brisanet Brazil
Twilio SMS delivery to Brisanet network subscribers in Brazil had delays and failures. The incident affected SMS in Latin America and the carrier network for SMS in Latin America. Twilio reports that the incident is resolved. It lasted about 6 hours and 40 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