Deepgram incident

Degraded performance — Flux streaming Speech-to-Text

Minor Resolved Upstream link ↗

Started

June 15, 2026 at 11:00 AM UTC

Duration

1d 2h

Resolved

June 16, 2026 at 02:00 PM UTC

Updates timeline

  1. Investigating

    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

    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

    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.

Live Deepgram status

Current indicator + 24h latency

All incidents

Cross-service timeline

Subscribe via RSS

Atom feed for any reader