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

As listed on Deepgram’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Deepgram status & history page.

Related: Deepgram status & history. SquidGrid is not affiliated with Deepgram.