Live

MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Carriers in United States

0

Twilio reports MMS delivery receipt delays from a subset of Twilio Long Codes to subscribers on multiple small carriers in the United States. The affected components are MMS Long Code, North America. Twilio identified the cause and continues to work on a fix. Messages may arrive, but delivery receipts may be delayed.

State

Identified

Started

Ongoing for

1 h 44 min

Worst impact

Degraded

Timeline

3 updates
22:5123:1723:4300:0900:35
DegradedUpdate postedTimes in UTC

Identified

1 h 44 min 100%

Updates

Times in UTC

As posted by Twilio

Identified

We are continuing to work on a fix for this issue.

Identified

Twilio customers may be experiencing MMS delivery delays from a subset of Twilio Long Codes to network subscribers on multiple Small Carriers 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.

Identified

Twilio customers may be experiencing MMS delivery receipt delays from a subset of Twilio Long Codes to network subscribers on multiple networks 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.

Affected components

3
MMS Long Code, North AmericaCARRIER NETWORK - MMS Long Code, North AmericaZIPWHIP MESSAGING - MMS Long Code, North America

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

71

Days with an incident

40

Median duration

7 h 20 min

This incident

76% 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 20 min
90 days agoToday

Other Twilio incidents

All incidents

Twilio·MMS Delivery Failures from a Subset of Twilio Long Codes to GCI United States

Twilio MMS delivery failures affect a subset of Twilio Long Codes to GCI network subscribers in the United States. This affects MMS Long Code in North America. Twilio reports that the team is investigating the issue.

Degraded

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

Twilio MMS delivery and MMS delivery receipts are delayed for a subset of Twilio Long Codes and Short Codes to AT&T subscribers in the United States. The affected components include MMS Long Code and MMS Short Code in North America. Twilio reports a recovery and monitors service stability.

Degraded

Twilio·MMS Delivery Delays and Failures from a Subset of Twilio Short Codes to T-Mobile and Verizon United States

MMS delivery delays and failures affected a subset of Twilio Short Codes to T-Mobile and Verizon subscribers in the United States. Twilio reports that the incident is resolved. The incident lasted about 6 hours and 18 minutes.

Resolved

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

Twilio SMS delivery delays affected a subset of Short Codes and Long Codes to Brisanet network subscribers in Brazil. Twilio reported the incident as resolved after about 14 hours and 47 minutes.

Resolved

Twilio·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Networks United States

MMS delivery from a subset of Twilio Long Codes to multiple small networks in the United States did not work. The incident is resolved. It lasted about 16 hours and 15 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