← Back to Twilio History
minor✓ Resolved
V3 Transcription API experiencing service issues
Status
resolved
Duration
6h 23m
Updates
2
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedFri, Jun 19, 2026, 01:10 AM
This incident has been resolved.
investigatingThu, Jun 18, 2026, 07:46 PM
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.
investigatingThu, Jun 18, 2026, 06:46 PM
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.
📊 TECHNICAL DETAILS
Internal ID
5557009e-2553-4f32-a144-f7bd94c26de0
External ID
yxxcf089rcjq
🕐 Started
Thu, Jun 18, 2026, 06:46 PM
🔄 Last Updated
Fri, Jun 19, 2026, 01:10 AM
✓ Resolved
Fri, Jun 19, 2026, 01:10 AM
MINOR
Impact Level
6h 23m
Total Duration
2
Status Updates
Affected Components
REST API
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed