Issues Storing Real-Time Transcriptions in Conversational Intelligence

What to do

• Check whether you use Twilio Conversation Intelligence (classic). Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 37m it lasted.

  Anything that failed between 2026-05-18 09:10 UTC and 2026-05-18 10:46 UTC may need a replay.

• Subscribe to Twilio's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=twilio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Twilio 3

1. investigatingMay 18, 2026, 9: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.

   provider

2. monitoringMay 18, 2026, 9: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.

   provider

3. resolvedMay 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.