MMS Delivery Receipt Delays from a Subset of Twilio Long Codes to GCI Communication United States
Twilio reports delayed MMS delivery receipts from a subset of Twilio Long Codes to GCI Communication subscribers in the United States. The MMS Long Code components in North America are affected. Twilio has identified the cause and work continues. Delivery can succeed, but receipts can arrive late.
State
Identified
Started
1 h ago
2026-11-03 04:46 UTC
Ongoing for
1 h 10 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
4 min 6%
Identified
1 h 6 min 94%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing MMS delivery receipt delays from a subset of Twilio Long Codes to GCI Communication 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 2 hours or as soon as more information becomes available.
Twilio customers may be experiencing MMS delivery receipt delays from a subset of Twilio Long Codes to GCI Communication 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 to GCI Communication 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
3Twilio in the last 90 days
Full historyIncidents in 90 days
67
Days with an incident
39
Median duration
6 h 32 min
This incident
82% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil
Twilio reports SMS delivery delays from a subset of Twilio Short Codes and Long Codes to Brisanet subscribers in Brazil. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio identified the cause and is working to resolve the issue.
Twilio·SMS Delivery Delays from Twilio to Entel Bolivia
Twilio SMS messages to Entel network subscribers in Bolivia have delivery delays. The SMS and carrier network components in Latin America are affected. Twilio reports that it identified the cause and is working to resolve the issue.
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.
Twilio·Voice Call Audio Quality Degradation from Network Subscribers to Twilio Phone Numbers
Voice calls from network subscribers to Twilio phone numbers have audio delays and high packet loss. The issue affects Voice and carrier network components in North America, Latin America, APAC, Europe, and Middle East & Africa. Twilio reports a recovery in these calls and continues to monitor service stability.
Twilio·RateQueue Host Down Did Not Recover
Twilio reports delays for SMS and Programmable Messaging SMS. No messages are lost. Twilio identified and mitigated the issue, and continues to investigate the root cause.
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.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.
https://outages.cc/feed.xml?providers=twilio/feed subscribe https://outages.cc/feed.xml?providers=twilioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane