Degraded performance , Flux streaming Speech-to-Text
Jun 15, 11:00 UTCJun 16, 14:00 UTC
Duration
27h
Impact
Minor
Root cause
Not disclosed
Deepgram, 90 days
19 incidents
Affected
Streaming APIDeepgram Public API (api.deepgram.com) - Streaming API
Final update
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.
Timeline
- Resolved · Jun 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.
- Identified · Jun 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.
- Investigating · Jun 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.
More from Deepgram
Full historyElevated errors for Flux streaming STT and Voice Agent sessionslasted 6h 33mElevated errors from authentication services at one datacenterlasted 55mElevated Latency and Errors for Batch STTlasted 2h 25mElevated 5xx Errorslasted 18h 59mElevated 503 errors for bath Flux TTS requestslasted 1h 31mElevated 503 errors for Aura-2 TTSlasted 11m