Issues Retrieving Transcripts

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 49m it lasted.

  Anything that failed between 2026-05-13 15:54 UTC and 2026-05-13 16:43 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 13, 2026, 3:54 PM UTC

   Our monitoring systems have detected a potential issue with Conversation intelligence v2 Dynamo db failures. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

   provider

2. monitoringMay 13, 2026, 4:10 PM UTC

   Some customers experienced issues retrieving transcripts between 15:04 and 15:46 UTC due to an issue with one of our Transcript Store services, this is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

   provider

3. resolvedMay 13, 2026, 4:43 PM UTC

   Issue Retrieving Transcripts has been resolved and 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.