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

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-06-15 11:00 UTC · Resolved: 2026-06-16 14:00 UTC · Duration: 27 h
- Updates: 3 · Affected components: Deepgram Public API (api.deepgram.com) - Streaming API, Streaming API
- [Vendor status page: https://stspg.io/4lqpkhj67qfq](https://stspg.io/4lqpkhj67qfq)
- [Company: Deepgram](https://rewindex.com/company/deepgram.md)

## Timeline of updates

- **investigating** 2026-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.
- **identified** 2026-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.
- **resolved** 2026-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.


---
Canonical: https://rewindex.com/company/deepgram/incidents/ywx3rwsxqk41 · Markdown: https://rewindex.com/company/deepgram/incidents/ywx3rwsxqk41.md · JSON: https://rewindex.com/api/v1/companies/deepgram/incidents/ywx3rwsxqk41 · Generated 2026-10-18T10:41:02.329Z