Twilio incident: SMS Delivery Delays and Failures from a Subset of Twilio Phone Numbers to China Mobile Hong Kong

1. resolvedMay 21, 2026, 11:45 UTC

   The incident has been resolved and SMS delivery from a subset of Twilio Phone Numbers to China Mobile network subscribers in Hong Kong is 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.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · May 19, 2026, 10:13 UTC
• Akamai: Configuration Deployment issues with EdgeWorkers and mPulse configuration activationsMinor · May 20, 2026, 14:29 UTC
• Vercel: Missing Build CPU Minutes Usage DataMinor · May 20, 2026, 20:07 UTC
• Supabase: Login issues for SSO and Email accounts on Supabase DashboardMinor · May 21, 2026, 08:30 UTC
• Intercom: Stale reporting dataMinor · May 21, 2026, 11:09 UTC
• Snyk: Snyk Import and Recurring Test DegradationMinor · May 21, 2026, 11:37 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