SendGrid: MMS Delivery Delays from a Subset of Twilio Long Codes to AT&T United States
Affected components: CARRIER NETWORK - MMS Long Code, North AmericaMMS Long Code, North America
Timeline of updates
- investigating
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 actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.
- investigating
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 actively investigating this issue. We will provide another update in 2 hours or as soon as more information becomes available.
- identified
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 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.
- identified
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 has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.
- identified
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 has identified the cause, and is working to resolve the issue. We will provide another update in 4 hours or as soon as more information becomes available.
- monitoring
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.
Changes Rewindex caught on this incident
- Oct 19Incident updated: MMS Delivery Delays from a Subset of Twilio Long Codes to AT&T United States
- Oct 19Incident updated: MMS Delivery Delays from a Subset of Twilio Long Codes to AT&T United States
- Oct 19Incident updated: MMS Delivery Delays from a Subset of Twilio Long Codes to AT&T United States
- Oct 20Incident updated: MMS Delivery Delays from a Subset of Twilio Long Codes to AT&T United States
- Oct 20Incident updated: MMS Delivery Delays from a Subset of Twilio Long Codes to AT&T United States
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured 20:33 UTC
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on Oct 20, 00:41 UTC. Record hash
c3e59630cf8f6ca9…Version 2 captured 21:33 UTC
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on Oct 20, 00:41 UTC. Record hash
91d6576013976d9d…Version 3 captured 21:43 UTC
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on Oct 20, 00:41 UTC. Record hash
c158693edd62f8b6…Version 4 captured 22:43 UTC
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on Oct 20, 00:41 UTC. Record hash
cb068c7de20d3893…
Rewindex captured a newer version after the last checkpoint; the next run (00:41 UTC) commits it.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).