V3 Transcription API experiencing service issues

What to do

• Check whether you use Twilio REST API in us. 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 6h 21m it lasted.

  Anything that failed between 2026-06-18 18:46 UTC and 2026-06-19 01:07 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. investigatingJun 18, 2026, 6:46 PM UTC

   Our monitoring systems have detected a potential issue with V3 transcriptions API failures. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

   provider

2. investigatingJun 18, 2026, 7:46 PM UTC

   We are investigating a service interruption with the V3 Transcriptions API. At this time, all batch transcription requests using the Google TTS chirp_2 (en-US) model are failing with PERMISSION_DENIED errors, resulting in a complete service outage for V3 transcription workflows. The root cause is a vendor-side issue as Google has blocked access to the chirp_2 model. We are actively working with our provider to resolve this and will provide another update once more information becomes available. If users are seeing issues with Google TTS chirp_2, using the Deepgram Nova3 language model is a potential workaround at this time.

   provider

3. resolvedJun 19, 2026, 1:07 AM UTC

   Service interruption with the V3 Transcriptions API 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.