Twilio incident: Issues Retrieving Transcripts

1. resolvedMay 13, 2026, 16:43 UTC

   Issue Retrieving Transcripts 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
• Cursor: Investigating Cloud Agent DegradationMajor · May 13, 2026, 16:06 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
• GitHub: Incident with CodeQLMinor · May 13, 2026, 14:41 UTC
• Snyk: Reporting PDF DegradedMinor · May 13, 2026, 14:49 UTC
• Supabase: Edge Traffic IssuesMinor · May 13, 2026, 16:15 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