Live

SMS Delivery Delays from a Subset of Twilio Short Codes to Multiple Networks in India

0

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 has identified the cause and is working to resolve the issue.

State

Identified

Started

Ongoing for

1 h 13 min

Worst impact

Degraded

Timeline

3 updates
15:3715:5516:1316:3216:50
DegradedUpdate postedTimes in UTC

Investigating

1 h 5 min 89%

Identified

8 min 11%

Updates

Times in UTC

As posted by Twilio

Identified

Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes 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.

Investigating

Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes to network subscribers on multiple networks in India. Our team is actively investigating this issue. We will provide another update in 2 hours or as soon as more information becomes available.

Investigating

Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes 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

2
SMS, APACCARRIER NETWORK - SMS, APAC

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

131

Days with an incident

49

Median duration

6 h 25 min

This incident

81% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

33 days
median 6 h 25 min
90 days agoToday

Other Twilio incidents

All incidents

Twilio·Silent Network Authentication (SNA) Failure Increase and Gateway API (Lookup API) Failure Increase in United Kingdom

Twilio Silent Network Authentication and Lookup API transactions fail in the United Kingdom. The affected components are Verify Silent Network Auth, Lookup Identity Match, Lookup SIM Swap, and Legacy Identity MatchAndAttributes. Twilio identified the cause and works to resolve the issue.

Degraded

Twilio·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.

Resolved

Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes to Multiple Networks in India

Twilio SMS delivery from a subset of Twilio Short Codes to multiple networks in India had delays. The SMS and carrier network components in APAC were affected. Twilio resolved the incident after 3 hours and 12 minutes.

Resolved

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.

Resolved

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.

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=twilio
Slack
/feed subscribe https://outages.live/feed.xml?providers=twilio

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane