Twilio incident: Subset of Inbound Calls from AT&T are Failing Shaken/Stir Verification

1. resolvedJun 3, 2026, 23:36 UTC

   The issues for Shaken/Stir verification failures for inbound calls originating from the AT&T network the United States has been resolved and it is operating normally at this time.

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.

• LaunchDarkly: Flag dashboard is failing to loadMajor · Jun 3, 2026, 19:31 UTC
• OVHcloud: [GRA/RBX/DE][Storage and Backups] - Object Storage Incident NotificationMinor · May 22, 2026, 15:04 UTC
• Linode: Service Issue - Block Storage Newark, USMinor · Jun 3, 2026, 08:58 UTC
• GitHub: Disruption with some GitHub servicesMinor · Jun 3, 2026, 19:42 UTC
• Grafana Cloud: K6 Test Runs Degraded PerformanceMinor · Jun 3, 2026, 20:40 UTC

How often does Twilio have incidents?

Twilio reported 501 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 5h 49m. See Twilio's uptime and incident history