Twilio incident: SMS Delivery Delays and Failures Between Twilio and Multiple Networks in Malaysia

1. resolvedMay 5, 2026, 14:33 UTC

   We have observed a recovery in SMS delivery between Twilio and network subscribers on multiple networks in Malaysia and are monitoring service stability. We will provide another update in 4 hours 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.

• GitHub: Incident with ActionsCritical · May 5, 2026, 13:37 UTC
• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Linode: (Copy Fail) Linux Kernel Local Privilege Escalation Vulnerability [CVE-2026-31431]Minor · May 1, 2026, 17:51 UTC
• Shippo: Royal Mail InterSoft Tracking Degradation (Third-Party Issue)Minor · May 4, 2026, 20:48 UTC
• Snowflake: Azure - West US 2 (Washington): INC0156645Minor · May 5, 2026, 04:12 UTC
• Contentful: Audit logs incomplete for days ranging between 30 of April and 4th of May.Minor · May 5, 2026, 13:13 UTC
• Upstash: QStash US Region: Schedule DegradationMinor · May 5, 2026, 14:24 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