SMS Delivery Failures from Twilio 10DLC to AT&T United States
Twilio reports SMS delivery failures from Twilio 10DLC to AT&T subscribers in the United States. The failures affect SMS Long Code, North America and CARRIER NETWORK - SMS Long Code, North America. Twilio identified the cause and is working to resolve the issue.
State
Identified
Started
Ongoing for
1 h 51 min
Worst impact
Degraded
Timeline
2 updatesIdentified
1 h 51 min 100%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing SMS delivery failures from Twilio 10DLC to AT&T network subscribers in the United States. 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 failures from Twilio 10DLC to AT&T network subscribers 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
117
Days with an incident
48
Median duration
6 h 32 min
This incident
72% shorter than the median
Other Twilio incidents
All incidentsTwilio·MMS Delivery Failures from Twilio to GCI United States
Twilio MMS delivery to GCI network subscribers in the United States failed. The affected components were MMS Long Code, MMS Short Code, and MMS Toll-Free in North America, and their carrier network links. Twilio reports that the incident is resolved. It lasted about 4 minutes.
Twilio·SMS Delivery Failures from Twilio to Orange Sierra Leone
Twilio reports SMS delivery failures from Twilio to Orange network subscribers in Sierra Leone. This affects SMS in the Middle East and Africa and the related carrier network. Twilio is investigating the issue. The incident started 62 minutes ago and is not resolved.
Twilio·SMS Delivery Failures From Long Code Numbers to AT&T in the US
Twilio reported SMS delivery failures from Long Code numbers to AT&T in the US. The incident affected SMS Long Code in North America. Twilio reports that the incident is resolved. It lasted about 79 minutes.
Twilio·SMS Delivery Delays from Twilio to MTS Kazakhstan
Twilio reports SMS delivery delays from Twilio to MTS network subscribers in Kazakhstan. The APAC SMS and carrier network SMS components are affected. Twilio is investigating the issue.
Twilio·SMS Delivery Failures from a Subset of Twilio Phone Numbers to Tcell Tajikistan
SMS delivery fails from some Twilio phone numbers to Tcell network subscribers in Tajikistan. The affected components are SMS, APAC and CARRIER NETWORK - SMS, APAC. Twilio reports that the incident is under investigation.
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