← Back to Twilio History
minor✓ Resolved

Speech Recognition and Real-Time Transcription Failures in US1

Twilio•
Status
resolved
Duration
2h 48m
Updates
4
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
We have monitored and resolved the issue with speech recognition and real-time transcription features in US1. All services are now operating normally at this time.
monitoring
Our engineers have mitigated the issue and are monitoring system performance. Speech recognition and real-time transcription services in US1 are returning to normal, and transcription processing for call recordings may continue to complete more slowly while systems stabilize. We will provide another update in 2 hours or as soon as more information becomes available.
identified
We have identified the issue of speech recognition failures for Voice in US1. Customers may experience no speech result when using `<Gather input="speech">`, and real-time transcription sessions may start without the first few seconds of audio transcribed or continue with a different transcription engine. Post-call transcriptions may also complete more slowly than usual. As a workaround, customers may use an alternative speech recognition provider where configurable. We will provide another update in 1 hour or as soon as more information becomes available.
investigating
We are investigating an issue with speech recognition and real-time transcription in US1. Users may experience failures with speech-to-text processing affecting <Gather> and real-time transcription. We will provide another update in 1 hour or as soon as more information becomes available.

📊 TECHNICAL DETAILS

Internal ID
6dda8acb-64fd-4b99-883d-0764130eb514
External ID
br82nbf55nll
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
2h 48m
Total Duration
4
Status Updates
Affected Components
Realtime TranscriptionsRecording Transcriptions US1Speech Recognition (Gather Speech) US1Realtime Transcriptions US1
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed