Twilio incident: Degradation to multiple Twilio products

1. resolvedMay 8, 2026, 08:36 UTC

   This incident has been resolved, and all affected services 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.

• ReadMe: Issues Creating New ChangelogsCritical · May 7, 2026, 23:43 UTC
• Datadog: Delayed Monitors NotificationsCritical · May 8, 2026, 00:06 UTC
• Convex: Intermittent Impact from AWS OutageMajor · May 8, 2026, 00:16 UTC
• Cursor: Investigating Service DegradationMajor · May 8, 2026, 00:43 UTC
• 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
• RevenueCat: Increased API error rates due to reduced service capacity.Minor · May 8, 2026, 00:51 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