MMS Delivery Delays from a Subset of Twilio Long Codes to AT&T United States
The incident has been resolved and MMS delivery from a subset of Twilio Long Codes to AT&T network subscribers in the United States is operating normally.
The latest update from SendGrid.
State
Resolved
Started
5 d ago
2026-10-27 12:58 UTC
Lasted
4 h 35 min
until 2026-10-27 17:32 UTC
Worst impact
Degraded
Timeline
7 updatesInvestigating
1 h 7 min 25%
Identified
1 h 25 min 31%
Monitoring
2 h 2 min 44%
Updates
Times in UTCAs posted by SendGrid
The incident has been resolved and MMS delivery from a subset of Twilio Long Codes to AT&T network subscribers in the United States is operating normally.
We have observed a recovery in MMS delivery from a subset of Twilio Long Codes to AT&T network subscribers in the United States and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
Twilio customers may be experiencing MMS delivery delays from a subset of Twilio Long Codes to AT&T network subscribers in the United States. Our team is continuing to investigate this issue. We will provide another update in 2 hours or as soon as more information becomes available.
wilio customers may be experiencing MMS delivery delays from a subset of Twilio Long Codes to AT&T network subscribers in the United States. Our team is continuing to investigate 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 from a subset of Twilio Long Codes to AT&T network subscribers in the United States. Our team is continuing to investigate this issue. We will provide another update in 2 hours or as soon as more information becomes available.
Twilio customers may be experiencing SMS and MMS delivery delays from a subset of Twilio Long 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 2 hours or as soon as more information becomes available.
Twilio customers may be experiencing SMS delivery receipt delays from a subset of Twilio Long 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
2SendGrid in the last 90 days
Full historyIncidents in 90 days
50
Days with an incident
37
Median duration
9 h 43 min
This incident
53% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·Silent Network Authentication (SNA) Missing Redirects and Gateway API (Lookup API) High Latency on KPN in Netherlands
The incident has been resolved and API transactions for Silent Network Authentication (SNA) on KPN in Netherlands and Lookup API transactions involving KPN in Netherlands are operating normally.
SendGrid·Silent Network Authentication (SNA) Missing Redirects on Smart in Philippines
The incident has been resolved and API transactions for Silent Network Authentication (SNA) on Smart in Philippines are operating normally.
SendGrid·Automated Alert: Minimal Customer Impact
We have fully investigated the issue affecting verifications to Ivory Coast, and it was determined that the impact was limited to a small set of customers, who have been contacted individually to address any concerns. All systems are operational.
SendGrid·SMS and MMS Delivery Delays from Twilio to Altice United States
The incident has been resolved and SMS and MMS delivery from Twilio to Altice network subscribers in the United States is operating normally.
SendGrid·SMS Delivery Receipt Delays from Twilio to Multiple Networks in Multiple Countries Across Africa and Asia
The incident has been resolved and SMS delivery receipts from Twilio to network subscribers on affected networks in multiple countries across Africa and Asia are operating normally.
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