Twilio incident: Customer Low Balance Notification and Automatic Recharge of Balance Is Not Working

1. resolvedMay 13, 2026, 11:23 UTC

   The issue affecting low balance notifications and the automatic balance recharge feature has been resolved and is operating normally at this time.

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
• Anthropic: Elevated errors for Claude Sonnet 4.6 and Haiku 4.5Major · May 12, 2026, 19:36 UTC
• Render: Logs unavailable for some services in all regionsMajor · May 12, 2026, 22:29 UTC
• Anthropic: Elevated errors on Claude Opus 4.7Major · May 12, 2026, 23:38 UTC
• OVHcloud: [GRA][Compute - Instance] - Incident NotificationMajor · May 13, 2026, 09:44 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
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Akamai: Bot Manager Premier IssuesMinor · May 11, 2026, 16:03 UTC
• ReadMe: Degraded performance across Admin HubsMinor · May 12, 2026, 14:15 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