Twilio incident: Network Degradation Between Regions Impacting Voice Calls, Video Sessions & Webhooks

1. resolvedMay 9, 2026, 12:21 UTC

   The incident affecting cross region connectivity has now been resolved. Customers will no longer experience degradation of calls, video calls or dropped Webhooks traversing between regions.

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.

• Supabase: Network connectivity in us-east-1-az4Major · May 8, 2026, 00:50 UTC
• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Shippo: Royal Mail InterSoft Tracking Degradation (Third-Party Issue)Minor · May 4, 2026, 20:48 UTC
• Snyk: Snyk Recurring Tests DelayedMinor · May 6, 2026, 15:32 UTC
• MongoDB Atlas: AWS Availability Zone use1-az4 in US-EAST-1 Region is ImpairedMinor · May 8, 2026, 02:24 UTC
• ClickHouse Cloud: Increased Error Rate and Latency on AWS Region (US-EAST-1)Minor · May 8, 2026, 02:46 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Vercel: Vercel Queues, and Vercel Workflow runs were delayedMinor · May 9, 2026, 04:45 UTC
• Anthropic: Elevated errors on Claude Opus 4.1Minor · May 9, 2026, 07:57 UTC

How often does Twilio have incidents?

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