MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Carriers in United States
SendGrid reported MMS delivery delays from a subset of Twilio Long Codes to multiple small carriers in the United States. The affected components were MMS Long Code, North America. SendGrid resolved the incident after 78 minutes.
State
Resolved
Started
Lasted
1 h 18 min
Worst impact
Degraded
Timeline
4 updatesIdentified
1 h 18 min 100%
Updates
Times in UTCAs posted by SendGrid
We are continuing to work on a fix for this issue.
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.
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
3SendGrid in the last 90 days
Full historyIncidents in 90 days
70
Days with an incident
40
Median duration
9 h 36 min
This incident
86% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·MMS Delivery Delays from a Subset of Twilio Long Codes and Short Codes to AT&T United States
SendGrid MMS messages from a subset of Twilio Long Codes and Short Codes to AT&T subscribers in the United States had delivery delays. The incident is resolved. It lasted about 8 hours and 26 minutes.
SendGrid·MMS Delivery Delays and Failures from a Subset of Twilio Short Codes to T-Mobile and Verizon United States
SendGrid reported that MMS delivery delays and failures affected MMS Short Code traffic in North America for a subset of Twilio Short Codes to T-Mobile and Verizon subscribers in the United States. SendGrid identified the cause and later saw a recovery in MMS delivery. SendGrid resolved the incident on 3 November 2026, about 6 hours and 18 minutes after it started.
SendGrid·SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil
SendGrid reported SMS delivery delays from a subset of Twilio Short Codes and Long Codes to Brisanet network subscribers in Brazil. The affected components were SMS, Latin America and CARRIER NETWORK - SMS, Latin America. SendGrid reported the incident as resolved after 14 hours and 47 minutes.
SendGrid·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Networks United States
SendGrid MMS messages from some Twilio Long Codes to subscribers on multiple small networks in the United States had delivery delays or failures. The MMS Long Code components in North America were affected. SendGrid reported the incident as resolved. The incident lasted about 16 hours and 15 minutes.
SendGrid·SMS Delivery Delays from Twilio to Entel Bolivia
SendGrid reports SMS delivery delays from Twilio to Entel network subscribers in Bolivia. The delays affect SMS in Latin America and the related carrier network. The incident is resolved and lasted about 9 hours and 37 minutes.
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