Companies / Deepgram / incidents

Deepgram: Degraded performance — Flux streaming Speech-to-Text

Affected components: Deepgram Public API (api.deepgram.com) - Streaming APIStreaming API

Timeline of updates

1. investigating2026-06-15 11:00 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.

2. identified2026-06-16 13:00 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.

3. resolved2026-06-16 14:00 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.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Deepgram profile · Recent Deepgram incidents · Markdown · JSON