Live

MMS Delivery Delays and Failures from a Subset of Twilio Long Codes and Short Codes to Multiple Networks in United States

0

Twilio MMS delivery delays and failures affect a subset of Twilio Long Codes and Short Codes to subscribers on multiple networks in the United States. The affected components are MMS Long Code, MMS Short Code, CARRIER NETWORK MMS Long Code and Short Code, and ZIPWHIP MESSAGING MMS Long Code in North America. Twilio is investigating the issue.

State

Investigating

Started

Ongoing for

1 h 53 min

Worst impact

Degraded

Timeline

2 updates
14:5115:1915:4816:1616:44
DegradedUpdate postedTimes in UTC

Investigating

1 h 53 min 100%

Updates

Times in UTC

As posted by Twilio

Investigating

Twilio customers may be experiencing MMS delivery delays and delivery failures from a subset of Twilio Long Codes and Short Codes to network subscribers on multiple networks in the United States. 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 MMS delivery delays and delivery failures from a subset of Twilio Long Codes and Short Codes to network subscribers on multiple networks in the United States. 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

5
MMS Long Code, North AmericaMMS Short Code, North AmericaCARRIER NETWORK - MMS Long Code, North AmericaCARRIER NETWORK - MMS Short Code, North AmericaZIPWHIP MESSAGING - MMS Long Code, North America

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

69

Days with an incident

39

Median duration

7 h 14 min

This incident

74% shorter than the median

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

33 days
median 7 h 14 min
90 days agoToday

Other Twilio incidents

All incidents

Twilio·MMS Delivery Receipt Delays from a Subset of Twilio Long Codes and Short Codes to AT&T United States

MMS delivery receipts do not work correctly for a subset of Twilio Long Codes and Short Codes in North America. The affected messages go to AT&T subscribers in the United States. Twilio reports that the cause is identified and that work to fix the problem is in progress. Message delivery can still succeed, but delivery receipts can be delayed.

Degraded

Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil

Twilio SMS delivery delays affect a subset of Twilio Short Codes and Long Codes to Brisanet network subscribers in Brazil. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio reports a recovery in SMS delivery and monitors service stability.

Degraded

Twilio·MMS Delivery Receipt Delays from a Subset of Twilio Long Codes to GCI Communication United States

Twilio MMS delivery receipts are delayed from a subset of Twilio Long Codes to GCI Communication subscribers in the United States. This affects MMS Long Code, CARRIER NETWORK, and ZIPWHIP MESSAGING in North America. Twilio has identified the cause and is working to resolve the issue.

Degraded

Twilio·SMS Delivery Delays from Twilio to Entel Bolivia

Twilio SMS delivery to Entel network subscribers in Bolivia had delays. The affected components were SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio reports that the incident is resolved. The delays lasted about 9 hours and 37 minutes.

Resolved

Twilio·SMS Delivery Delays from Twilio to Lycamobile United Kingdom

Twilio SMS delivery delays affected messages to Lycamobile subscribers in the United Kingdom. The affected components were SMS, Europe and CARRIER NETWORK - SMS, Europe. Twilio resolved the incident. The outage lasted about 2 hours and 40 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.cc/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.cc/feed.xml?providers=twilio
Slack
/feed subscribe https://outages.cc/feed.xml?providers=twilio

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane