Twilio incident

Issues Storing Real-Time Transcriptions in Conversational Intelligence

Minor Resolved View vendor source →

Twilio experienced a minor incident on May 18, 2026 affecting Intelligence US1, lasting 1h 36m. The incident has been resolved; the full update timeline is below.

Started
May 18, 2026, 09:10 AM UTC
Resolved
May 18, 2026, 10:46 AM UTC
Duration
1h 36m
Detected by Pingoru
May 18, 2026, 09:10 AM UTC

Affected components

Intelligence US1

Update timeline

  1. investigating May 18, 2026, 09:10 AM UTC

    We are currently investigating an issue where a small percentage of real-time transcripts generated via the transcription TwiML verb are failing to be stored in Conversational Intelligence. This is also preventing the subsequent intelligence analysis of those transcripts from being completed. Our team is actively working to resolve this service disruption, and we expect to provide another update in 2 hours or as soon as more information becomes available.

  2. monitoring May 18, 2026, 09:45 AM UTC

    Our engineers have implemented a fix and are monitoring system performance. We are currently seeing recovery for the storage of real-time transcripts and their subsequent intelligence analysis. We will provide another update in 2 hours or as soon as more information becomes available.

  3. resolved May 18, 2026, 10:46 AM 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.