Twilio incident: Silent Network Authentication (SNA) Failure Increase on AT&T in United States

Affected components

• Verify Silent Network Auth

1. resolvedOct 2, 2026, 15:04 UTC

   The incident has been resolved and API transactions for Silent Network Authentication (SNA) on AT&T in the United States are operating normally.

2. monitoringOct 2, 2026, 12:40 UTC

   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.

3. monitoringOct 2, 2026, 10:40 UTC

   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.

4. investigatingOct 2, 2026, 10:02 UTC

   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 4 hours or as soon as more information becomes available.

5. investigatingOct 2, 2026, 08:01 UTC

   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 2 hours or as soon as more information becomes available.

6. investigatingOct 2, 2026, 06:56 UTC

   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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Twilio's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Contentful: Issues with advanced caching on Content Delivery APIMajor · Oct 1, 2026, 09:27 UTC
• Shippo: USPS Tracking disruptionMajor · Oct 2, 2026, 05:36 UTC
• Telnyx: Cloud Storage us-west-1 Region Temporarily UnavailableMajor · Oct 2, 2026, 14:20 UTC
• Akamai: Origin Server Connectivity Issues with Elevated Errors in APAC RegionMinor · Sep 22, 2026, 14:28 UTC
• Cloudflare: Cloudflare One Clients are incorrectly challenged on some sitesMinor · Sep 22, 2026, 19:23 UTC
• Zoom: Service Degradation Affecting Customer Using Polycom Devices Going OfflineMinor · Sep 25, 2026, 17:45 UTC
• SendGrid: MMS Delivery Delays from a Subset of Twilio Long Codes to GCI United StatesMinor · Sep 26, 2026, 03:16 UTC
• Clerk: Development instances only - Apple rejecting emailsMinor · Sep 28, 2026, 15:23 UTC
• Supabase: Intermittent latency in Eastern USMinor · Sep 29, 2026, 16:26 UTC
• SendGrid: SMS Delivery Delays from a Subset of Twilio Phone Numbers to Vodafone NetherlandsMinor · Oct 2, 2026, 04:42 UTC

How often does Twilio have incidents?

Twilio reported 46 incidents in the last 90 days. A typical incident lasted 7h 1m. See Twilio's uptime and incident history