Twilio incident
V3 Transcription API experiencing service issues
Twilio experienced a minor incident on June 18, 2026 affecting REST API, lasting 6h 20m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 18, 2026, 06: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.
- investigating Jun 18, 2026, 07: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.
- resolved Jun 19, 2026, 01:07 AM UTC
Service interruption with the V3 Transcriptions API has been resolved and [product][service] is operating normally at this time.