MMS Delivery Receipt Delays from a Subset of Twilio Long Codes to GCI Communication United States
SendGrid reports MMS delivery receipt delays from a subset of Twilio Long Codes to GCI Communication subscribers in the United States. The affected components are MMS Long Code, North America. SendGrid identified the cause and is working to resolve the issue. Message delivery can succeed, but delivery receipts can be delayed.
State
Identified
Started
1 h ago
2026-11-03 04:46 UTC
Ongoing for
1 h 7 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
5 min 7%
Identified
1 h 2 min 93%
Updates
Times in UTCAs posted by SendGrid
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
3SendGrid in the last 90 days
Full historyIncidents in 90 days
67
Days with an incident
39
Median duration
6 h 32 min
This incident
83% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil
SendGrid reports SMS delivery delays from some Twilio Short Codes and Long Codes to Brisanet subscribers in Brazil. The Latin America SMS components are degraded. SendGrid identified the cause and is working to resolve the issue.
SendGrid·SMS Delivery Delays from Twilio to Entel Bolivia
SendGrid reports SMS delivery delays to Entel network subscribers in Bolivia. The SMS Latin America and carrier network components are affected. SendGrid has identified the cause and is working to resolve the issue.
SendGrid·SMS Delivery Delays from Twilio to Lycamobile United Kingdom
SendGrid reports SMS delivery delays from Twilio to Lycamobile network subscribers in the United Kingdom. The issue affected SMS in Europe and the carrier network for SMS in Europe. SendGrid reports that the incident is resolved. The incident lasted about 160 minutes.
SendGrid·Voice Call Audio Quality Degradation from Network Subscribers to Twilio Phone Numbers
SendGrid reports degraded audio quality on voice calls from network subscribers to Twilio phone numbers. The affected components are Voice and the carrier network in North America, Latin America, APAC, Europe, and the Middle East and Africa. SendGrid reports a recovery and monitors service stability.
SendGrid·RateQueue Host Down Did Not Recover
SendGrid reports delays for SMS and PROGRAMMABLE MESSAGING - SMS. No messages are lost. SendGrid identified and mitigated the issue, and continues to investigate the root cause.
Follow SendGrid
Your coding agent knows when SendGrid is down, and tells you when a failure is theirs, not yours. You can also get SendGrid 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 "sendgrid" and tell me if SendGrid 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=sendgrid/feed subscribe https://outages.live/feed.xml?providers=sendgridFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane