Twilio outage on October 20, 2026: Silent Network Authentication (SNA) Failure Increase on AT&T in United States
Twilio reported an incident affecting Twilio for 3 hours 17 minutes on 20 October 2026, from 05:28 to 08:45 UTC.
Resolved
Official incident reported by Twilio
- Started
- 05:28
- 20 Oct 2026 UTC
- Resolved
- 08:45
- 20 Oct 2026 UTC
- Duration
- 3h 17m
- 3 hours 17 minutes
- Impact
- Minor
- as rated by Twilio
- Updates
- 5
- posted by Twilio
Timeline
All times UTC.
Official incident from Twilio
Silent Network Authentication (SNA) Failure Increase on AT&T in United States
-
Official
Investigating
Twilio customers may be experiencing verification failures during API transactions for Silent Network Authentication (SNA) on AT&T in the United States. Our team is actively investigating the issue. API transactions may temporarily fail over to secondary methods like SMS OTP. We will provide another update in 1 hour or as soon as more information becomes available.
-
Official
Identified
Twilio customers may be experiencing verification failures during API transactions for Silent Network Authentication (SNA) on AT&T in the United States. API transactions may temporarily fail over to secondary methods like SMS OTP. 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.
-
Official
Monitoring
We have observed recovery in API transactions for Silent Network Authentication (SNA) on AT&T 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.
-
Official
Monitoring
We have observed recovery in API transactions for Silent Network Authentication (SNA) on AT&T in the United States and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.
-
Official
Resolved
The incident has been resolved and API transactions for Silent Network Authentication (SNA) on AT&T in the United States are operating normally.
"Official" rows are quoted from Twilio's public status page, status.twilio.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test www.twilio.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Twilio status shows what our checks see right now.
Does your product depend on Twilio?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with Twilio. Official updates are quoted from Twilio's public status page and remain Twilio's own words.