SendGrid: SMS Delivery Receipt Delays from Twilio to Multiple Networks in United States and Canada
Affected components: CARRIER NETWORK - SMS Long Code, North AmericaCARRIER NETWORK - SMS Short Code, North AmericaCARRIER NETWORK - SMS Toll-Free, North AmericaSMS Long Code, North AmericaSMS Short Code, North AmericaSMS Toll-Free, North America
Timeline of updates
- identified
Twilio customers may be experiencing SMS delivery receipt delays from Twilio to Altice 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.
- identified
Twilio customers may be experiencing SMS delivery receipt delays from Twilio 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.
- identified
Twilio customers may be experiencing SMS delivery receipt delays from Twilio to network subscribers on multiple networks in the United States and Canada. 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.
- identified
Twilio customers may be experiencing SMS delivery receipt delays from Twilio to network subscribers on multiple networks in United States of America & Canada. 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 2 hours or as soon as more information becomes available.
- identified
Twilio customers may be experiencing SMS delivery receipt delays from Twilio to network subscribers on multiple networks in multiple countries in North America. 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 4 hours or as soon as more information becomes available.
- monitoring
We have observed a recovery in SMS delivery receipts from Twilio to network subscribers on multiple networks in multiple countries in North America and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
- monitoring
We have observed a recovery in SMS delivery receipts from Twilio to network subscribers on multiple networks in multiple countries in North America and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.
- resolved
The incident has been resolved and SMS delivery receipts from Twilio to network subscribers on affected networks in the United States and Canada are operating normally.
Changes Rewindex caught on this incident
- Incident updated: SMS Delivery Receipt Delays from Twilio to Multiple Networks in United States
- Incident updated: SMS Delivery Receipt Delays from Twilio to Multiple Networks in United States and Canada
- Incident updated: SMS Delivery Receipt Delays from Twilio to Multiple Networks in United States of America & Canada
- Incident updated: SMS Delivery Receipt Delays from Twilio to Multiple Networks in Multiple Countries in North America
- Incident updated: SMS Delivery Receipt Delays from Twilio to Multiple Networks in Multiple Countries in North America
- Incident updated: SMS Delivery Receipt Delays from Twilio to Multiple Networks in Multiple Countries in North America
- Incident updated: SMS Delivery Receipt Delays from Twilio to Multiple Networks in United States and Canada
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
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
7053fb167c6c4f7c…Version 2 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
9ea89a585eb8f27f…Version 3 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
6fd2fe83b04d0f8d…Version 4 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
18768e9644e95791…Version 5 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
504d50441be94013…Version 6 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
969c554d318a5e5b…Version 7 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
e48901747e300f0e…Version 8 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
30ff820232e89190…
Impact, status and times are the vendor’s own, as last archived. View on status.sendgrid.com (opens in new tab).