Live / Twilio / Incident
Twilio: SMS Delivery Failures from Twilio Long Codes to AT&T United States
Twilio · twilio.comMinor incidentResolved2026-11-12 06:02 UTC
Public — what happened
Summary
Twilio said some customers may have had text messages fail to deliver when sent from its standard US business long-code numbers (10DLC) to people on the AT&T network in the United States. The company posted its first notice at 01:58 UTC on 2026-11-12 and said it had already identified the cause and was working on a fix. By 04:00 UTC Twilio said it had seen delivery recover and was watching to make sure service stayed stable, and the incident was marked resolved at 06:02 UTC.
Affected
SMS Long Code, North America
Timeline
- Started — 2026-11-12 01:58 UTC
- Identified — 2026-11-12 01:58 UTC (2 updates)
- Monitoring — 2026-11-12 04:00 UTC
- Resolved — 2026-11-12 06:02 UTC · 4h 04m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Twilio against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Twilio: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Twilio report →
More from Twilio
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.