Twilio incident: Issues Storing Real-Time Transcriptions in Conversational Intelligence

1. resolvedMay 18, 2026, 10:46 UTC

   The issue preventing the storage of real-time transcripts and their subsequent intelligence analysis has been resolved, and Conversational Intelligence 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
• OVHcloud: [EU-SOUTH-MILA/B/C][Compute - Instance] - Instance creation incident notificationMajor · May 18, 2026, 09:17 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
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• Grafana Cloud: Grafana K6 metrics processing and test runs degradationMinor · May 18, 2026, 08: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