MMS Delivery Delays and Failures from a Subset of Twilio Short Codes to T-Mobile and Verizon United States
MMS delivery delays and failures affect a subset of Twilio Short Codes that send to T-Mobile and Verizon subscribers in the United States. SendGrid reports that the cause is identified and the fix is in progress.
State
Identified
Started
Ongoing for
2 h 16 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
2 h 88%
Identified
16 min 12%
Updates
Times in UTCAs posted by SendGrid
Twilio customers may be experiencing MMS delivery delays and failures from a subset of Twilio Short Codes to T-Mobile and Verizon network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.
Twilio customers may be experiencing MMS delivery delays and delivery failures from a subset of Twilio Long Codes and Short Codes to network subscribers on multiple networks in the United States. Our team is actively investigating this issue. We will provide another update in 2 hours or as soon as more information becomes available.
Twilio customers may be experiencing MMS delivery delays and delivery failures from a subset of Twilio Long Codes and Short Codes to network subscribers on multiple networks 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
2SendGrid in the last 90 days
Full historyIncidents in 90 days
69
Days with an incident
39
Median duration
7 h 14 min
This incident
69% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·MMS Delivery Receipt Delays from a Subset of Twilio Long Codes and Short Codes to AT&T United States
MMS delivery receipts are delayed for a subset of SendGrid Long Codes and Short Codes that send to AT&T subscribers in the United States. SendGrid reports that the cause is identified and that work to fix the issue is in progress. Message delivery can still succeed, but delivery receipts can be delayed.
SendGrid·SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil
SendGrid reports SMS delivery delays from a subset of Twilio Short Codes and Long Codes to Brisanet network subscribers in Brazil. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. SendGrid reports a recovery in SMS delivery and monitors service stability.
SendGrid·MMS Delivery Failures from a Subset of Twilio Long Codes to Small Networks United States
SendGrid reports MMS delivery failures and delivery receipt delays from a subset of Twilio Long Codes to small network subscribers in the United States. The affected components are MMS Long Code, North America, plus its carrier network and Zipwhip messaging parts. SendGrid has identified the cause and is working to resolve the issue.
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.
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.
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