Deepgram outage, 5 November 2026

Elevated errors for Flux streaming STT and Voice Agent sessions

Started
Resolved
6 Nov 2026, 01:14 UTC (after 6 h 32 min)
Impact
Not stated
Affected
Streaming API, Voice Agent API

Is this still happening?

No. Deepgram marked this incident resolved on 6 Nov 2026, 01:14 UTC, 6 h 32 min after it began.

Right now: Deepgram reports all systems operational. (as of 13 Nov, 20:59 UTC) Live Deepgram status

At a glance

Our summary from the Deepgram incidents we have recorded since 22 May 2026 - how we count.

Last update from Deepgram

This incident has been resolved.

6 Nov 2026, 01:14 UTC

Read the full incident on the official Deepgram status page

Similar Deepgram incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 55 min

    Elevated errors from authentication services at one datacenter

  2. , resolved after 18 h 59 min

    Elevated 5xx Errors

  3. , resolved after 10 min

    Elevated API errors

  4. , resolved after 3 h 39 min

    [Deepgram API] Elevated Batch and Streaming STT Error Rates

  5. , resolved after 2 h 23 min

    Elevated 5XX Errors for Flux STT Requests

Other recent Deepgram incidents

  1. Flux TTS high latency and websocket disconnects

  2. Flux TTS high latency and websocket disconnects

  3. Elevated Latency and Errors for Batch STT

  4. Elevated 503 errors for bath Flux TTS requests

  5. Elevated 503 errors for Aura-2 TTS

  6. Elevated error rates for Flux TTS

  7. Elevated errors for Flux TTS

  8. Elevated errors for Flux TTS

All recorded Deepgram incidents

Something wrong on this page?

A person reads every report. We fix our own mistakes - wording, mapping, a moved status page; the status itself always comes from Deepgram's official page. How we handle corrections.

Thanks - your report is on its way to us. We read every one.