Issue with Realtime Transcriptions and Deepgram

What to do

• Check whether you use Twilio Realtime Transcriptions, Speech Recognition (Gather Speech) US1, Realtime Transcriptions US1. 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 36m it lasted.

  Anything that failed between 2026-10-22 16:32 UTC and 2026-10-22 18:08 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. investigatingOct 22, 2026, 4:32 PM UTC

   Our monitoring systems have detected a potential issue with realtime transcription and Deepgram. Our engineers have been alerted and are investigating. We will provide an update when we have more details. Customers are recommended to move to Google as a temporary workaround until we have additional details.

   provider

2. monitoringOct 22, 2026, 5:38 PM UTC

   We have mitigated the issue and are monitoring system performance. Speech recognition for Voice calls is returning to normal. We will provide another update in 30 minutes or as soon as more information becomes available.

   provider

3. resolvedOct 22, 2026, 6:08 PM UTC

   The issue affecting realtime transcriptions and Deepgram has been resolved, and the service is functioning 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.