MMS Delivery Receipt Delays from a Subset of Twilio Long Codes and Short Codes to AT&T United States
Twilio MMS delivery receipts are delayed for a subset of Twilio Long Codes and Short Codes to AT&T subscribers in the United States. MMS Long Code and MMS Short Code in North America are affected. Twilio has identified the cause and is working to resolve the issue. Message delivery can succeed, but delivery receipts can be delayed.
State
Identified
Started
Ongoing for
1 h 27 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
59 min 68%
Identified
28 min 32%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing MMS delivery receipt delays from a subset of Twilio Long Codes and Short Codes to AT&T network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 1 hour or as soon as more information becomes available.
Twilio customers may be experiencing MMS delivery receipt delays from a subset of Twilio Long Codes and Short Codes to AT&T network subscribers in the United States. Our team is actively investigating this issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 1 hour or as soon as more information becomes available.
Affected components
4Twilio in the last 90 days
Full historyIncidents in 90 days
69
Days with an incident
39
Median duration
7 h 14 min
This incident
80% shorter than the median
Other Twilio incidents
All incidentsTwilio·MMS Delivery Delays and Failures from a Subset of Twilio Short Codes to T-Mobile and Verizon United States
Twilio MMS delivery delays and failures affect a subset of Twilio Short Codes to T-Mobile and Verizon subscribers in the United States. The affected components are MMS Short Code, North America and CARRIER NETWORK - MMS Short Code, North America. Twilio reports the status as identified and is working to resolve the issue.
Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil
Twilio reports SMS delivery delays from some Twilio Short Codes and Long Codes to Brisanet network subscribers in Brazil. This affects SMS in Latin America and the carrier network for SMS in Latin America. Twilio has identified the cause and reports a recovery in delivery. Twilio is monitoring service stability.
Twilio·MMS Delivery Failures from a Subset of Twilio Long Codes to Small Networks United States
Twilio MMS Long Codes in North America have MMS delivery failures to small network subscribers in the United States. Twilio has identified the cause and is working to resolve the issue.
Twilio·SMS Delivery Delays from Twilio to Entel Bolivia
Twilio SMS delivery to Entel network subscribers in Bolivia had delays. The incident affected SMS in Latin America and the carrier network for SMS in Latin America. Twilio reports that the incident is resolved and that the service operates normally. The incident lasted about 9 hours and 37 minutes.
Twilio·SMS Delivery Delays from Twilio to Lycamobile United Kingdom
Twilio SMS delivery to Lycamobile United Kingdom subscribers had delays. The affected components were SMS, Europe and Carrier Network SMS, Europe. Twilio reports that the incident is resolved, and the delays lasted about 160 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