Live / Deepgram / Incident
Deepgram: Elevated errors for Flux streaming STT and Voice Agent sessions
Deepgram · deepgram.comResolved2026-11-06 01:14 UTC
Public — what happened
Summary
Deepgram said it began looking into a rise in errors affecting its Flux streaming speech-to-text service at its US endpoint at 18:42 UTC on November 5, 2026. The company said Voice Agent sessions set up to use a Flux listening model might fail to start, and that its other models were not affected. Deepgram reported at 18:51 UTC that it had put a fix in place and was watching the results, and the incident is marked resolved as of 01:14 UTC on November 6. The company did not state a cause in the text provided.
Affected
Streaming API, Voice Agent API
Timeline
- Started — 2026-11-05 18:42 UTC
- Investigating — 2026-11-05 18:42 UTC
- Monitoring — 2026-11-05 18:51 UTC
- Resolved — 2026-11-06 01:14 UTC · 6h 33m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Deepgram against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Deepgram: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Deepgram report →
More from Deepgram
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.