MMS Delivery Failures from a Subset of Twilio Long Codes to GCI United States
MMS delivery failures affected a subset of Twilio Long Codes that send to GCI network subscribers in the United States. Twilio reports that the incident is resolved. The outage lasted about 32 minutes.
State
Resolved
Started
Lasted
32 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
32 min 100%
Updates
Times in UTCAs posted by Twilio
The incident has been resolved and MMS delivery from a subset of Twilio Long Codes to GCI network subscribers in the United States is operating normally.
Twilio customers may be experiencing MMS delivery failures from a subset of Twilio Long Codes to GCI network subscribers 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
3Twilio in the last 90 days
Full historyIncidents in 90 days
71
Days with an incident
40
Median duration
7 h 20 min
This incident
93% shorter than the median
Other Twilio incidents
All incidentsTwilio·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Networks in United States
Twilio MMS delivery receipts are delayed from some Twilio Long Codes to subscribers on small networks in the United States. This affects MMS Long Code, North America and CARRIER NETWORK - MMS Long Code, North America. Twilio identified the cause and continues to work on a fix. The issue started 105 minutes ago.
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.
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.
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.
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.
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