Twilio incident: Voice Call Failures and Audio Quality Degradation Between a Subset of Twilio Hong Kong Phone Numbers and Multiple Networks in Hong Kong

1. resolvedAug 31, 2026, 14:35 UTC

   The incident has been resolved and voice calls between a subset of Twilio Hong Kong Phone Numbers and network subscribers on affected networks in Hong Kong are operating normally.

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: Increased response times for requestsMajor · Aug 27, 2026, 17:20 UTC
• Shippo: Elevated error rate on DPD UK TrackingMajor · Aug 28, 2026, 04:41 UTC
• Supabase: Projects failing to load Supautils in multiple regionsMajor · Aug 28, 2026, 16:18 UTC
• Grafana Cloud: Partial Logs Write OutageMajor · Aug 28, 2026, 17:12 UTC
• Anthropic: Elevated errors on Claude Code and Claude CoworkMajor · Aug 28, 2026, 17:22 UTC
• Shippo: Elevated error rate on Canada Post ShipmentMajor · Aug 28, 2026, 19:27 UTC
• Upstash: Message Persistence Issue — QStash us-east-1Major · Aug 28, 2026, 22:56 UTC
• Notion: We’re aware of an issue that is causing some Notion AI MCP tool calls to fail.Major · Aug 30, 2026, 16:13 UTC
• Miro: Intermittent Issues with User Registration and LoginMajor · Aug 31, 2026, 14:31 UTC
• Akamai: Reporting data availability issues in 'Traffic by Hostname' reportMinor · Aug 20, 2026, 16:43 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 49m. See Twilio's uptime and incident history