Twilio incident: Twilio Accounts May Not Be Able to Capture Speech Using <gather>

1. resolvedMay 13, 2026, 22:10 UTC

   We have fully investigated the issue where Twilio accounts may not be able to capture speech using "gather" verb, and it was determined that there is no noticeable customer impact. All systems are operational.

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
• 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
• Grafana Cloud: Intermittent Errors and High latency Writing to Cloud Metrics, Cloud Logs and Cloud TracesMinor · May 13, 2026, 08:50 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 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