Twilio: Silent Network Authentication (SNA) Failure Increase on AT&T in United States
Affected components: CARRIER NETWORK - Verify Silent Network AuthVerify Silent Network Auth
Timeline of updates
- 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.
- 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.
- 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.
- 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.
- resolved
The incident has been resolved and API transactions for Silent Network Authentication (SNA) on AT&T in the United States are operating normally.
Changes Rewindex caught on this incident
- Incident updated: Silent Network Authentication (SNA) Failure Increase on AT&T in United States
- Incident updated: Silent Network Authentication (SNA) Failure Increase on AT&T in United States
- Incident updated: Silent Network Authentication (SNA) Failure Increase on AT&T in 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
In the 2026-10-20 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
55fc9a5b00d7c657…Version 2 captured
In the 2026-10-20 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d1729d407bcd39e0…Version 3 captured
In the 2026-10-20 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
c23d993c919b9407…Version 4 captured
In the 2026-10-20 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
3f6169bd53290da9…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Twilio, started 2026-10-20 05:28 UTC, resolved after 3.3 h, 5 update(s); edited after publishing.
- Title
- Silent Network Authentication (SNA) Failure Increase on AT&T in United States
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/sf1wgpv8z8hr
Twilio profileRecent Twilio incidentsAll outages on October 20, 2026Twilio in October 2026MarkdownJSON