Deepgram Voice AI incident

Degraded performance — Flux streaming Speech-to-Text

Minor Resolved View vendor source →

Deepgram Voice AI experienced a minor incident on June 15, 2026 affecting Streaming API, lasting 1d 2h. The incident has been resolved; the full update timeline is below.

Started
Jun 15, 2026, 11:00 AM UTC
Resolved
Jun 16, 2026, 02:00 PM UTC
Duration
1d 2h
Detected by Pingoru
Jun 15, 2026, 11:00 AM UTC

Affected components

Streaming API

Update timeline

  1. 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.

  2. 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.

  3. 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.