Degraded performance — Flux streaming Speech-to-Text
minor- Started
- Jun 15, 7:00 AM EDT
- Resolved
- Jun 16, 10:00 AM EDT
- Duration
- 27h
Deepgram's updates (3)
- investigating · Jun 15, 7:00 AM EDT
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 16, 9:00 AM EDT
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 16, 10:00 AM EDT
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.
Updates are Deepgram's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗