MMS Delivery Receipt Delays from a Subset of Twilio Long Codes and Short Codes to AT&T United States
SendGrid reports delays to MMS delivery receipts from a subset of Twilio long codes and short codes to AT&T subscribers in the United States. The affected components are MMS long code and short code in North America. SendGrid identified the cause and works to resolve the issue.
State
Identified
Started
Ongoing for
1 h 49 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
59 min 54%
Identified
51 min 46%
Updates
Times in UTCAs posted by SendGrid
Twilio customers may be experiencing MMS delivery receipt delays from a subset of Twilio Long Codes and Short Codes to AT&T 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 and Short Codes to AT&T 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
4SendGrid in the last 90 days
Full historyIncidents in 90 days
69
Days with an incident
39
Median duration
7 h 14 min
This incident
75% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·MMS Delivery Delays and Failures from a Subset of Twilio Short Codes to T-Mobile and Verizon United States
SendGrid reports MMS delivery delays and failures from a subset of Twilio short codes to T-Mobile and Verizon subscribers in the United States. The affected components are MMS Short Code, North America and CARRIER NETWORK - MMS Short Code, North America. SendGrid has identified the cause and is working to resolve the issue.
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 has identified the cause and reports a recovery. SendGrid monitors service stability.
SendGrid·MMS Delivery Failures from a Subset of Twilio Long Codes to Small Networks United States
SendGrid reports MMS delivery failures from a subset of Twilio Long Codes to small network subscribers in the United States. The affected components are MMS Long Code in North America, the carrier network for MMS Long Code in North America, and ZIPWHIP MESSAGING MMS Long Code in North America. SendGrid has identified the cause and works to resolve the issue.
SendGrid·SMS Delivery Delays from Twilio to Entel Bolivia
SendGrid reported SMS delivery delays from Twilio to Entel network subscribers in Bolivia. The incident affected SMS services in Latin America and the carrier network. SendGrid resolved the incident. The outage lasted 9 hours and 37 minutes.
SendGrid·SMS Delivery Delays from Twilio to Lycamobile United Kingdom
SendGrid reports SMS delivery delays to Lycamobile United Kingdom subscribers on the Europe SMS and carrier network components. SendGrid later reported a recovery and monitored stability. SendGrid reports that this incident is resolved. The incident lasted about 2 hours and 40 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.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 "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.cc/feed.xml?providers=sendgrid/feed subscribe https://outages.cc/feed.xml?providers=sendgridFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane