Deepgram outage, 10 November 2026

Flux TTS high latency and websocket disconnects

Started
Resolved
10 Nov 2026, 03:20 UTC (after 10 min)
Impact
Major
Affected
TTS API

Is this still happening?

No. Deepgram marked this incident resolved on 10 Nov 2026, 03:20 UTC, 10 min after it began.

Right now: Deepgram reports all systems operational. (as of 13 Nov, 20:53 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

Flux TTS disconnects occurred between 03:10 - 03:20, with high Flux TTS latency leading up to 03:10. The issue is now resolved.

10 Nov 2026, 03:20 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. , still open

    Flux TTS high latency and websocket disconnects

  2. , resolved after 1 h 30 min

    Elevated 503 errors for bath Flux TTS requests

  3. , resolved after 1 h 27 min

    Elevated error rates for Flux TTS

  4. , resolved after 2 h

    Elevated errors for Flux TTS

  5. , resolved after 2 h

    Elevated errors for Flux TTS

Other recent Deepgram incidents

  1. Elevated errors for Flux streaming STT and Voice Agent sessions

  2. Elevated errors from authentication services at one datacenter

  3. Elevated Latency and Errors for Batch STT

  4. Elevated 5xx Errors

  5. Elevated 503 errors for Aura-2 TTS

  6. Elevated API errors

  7. Elevated Latency and Errors for Batch STT (US)

  8. Elevated latency on Flux STT (US)

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.