Deepgram Voice AI incident
Degraded performance — Flux streaming Speech-to-Text
Resolved after 1 day 2 hours, affecting Streaming API, on June 15, 2026.
This incident has been resolved. A degradation affecting a subset of streaming Speech-to-Text (Flux) sessions, where connections terminated before returning a transcript, has been mitigated and service has been operating normally since. We're continuing to monitor and apologize for the disruption.
Affected components
Update timeline
- investigating Jun 17, 2026, 07:02 PM UTC
Some streaming Speech-to-Text connections on the Flux model established successfully but then terminated a few seconds into the session due to an internal error, before returning a final transcript. Applications relying on final transcripts (e.g. IVR/voice-agent flows) would have seen sessions open with no transcript returned.
- identified Jun 17, 2026, 07:04 PM UTC
We identified a degradation affecting a subset of Flux streaming Speech-to-Text sessions, where connections terminated before returning a transcript. We've isolated it to specific degraded hosts and are mitigating.
- resolved Jun 17, 2026, 07:13 PM UTC
This incident has been resolved. A degradation affecting a subset of streaming Speech-to-Text (Flux) sessions, where connections terminated before returning a transcript, has been mitigated and service has been operating normally since. We're continuing to monitor and apologize for the disruption.
Your product runs on more than Deepgram Voice AI
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services