Deepgram outage, 29 October 2026

Elevated errors from authentication services at one datacenter

Started
Resolved
29 Oct 2026, 16:12 UTC (after 55 min)
Impact
Minor
Affected
Batch API, Streaming API, TTS API, Voice Agent API, Voice Agent API: Downstream Providers, DG Whisper Cloud

Is this still happening?

No. Deepgram marked this incident resolved on 29 Oct 2026, 16:12 UTC, 55 min after it began.

Right now: Deepgram reports all systems operational. (as of 29 Oct, 17:57 UTC) Live Deepgram status

Last update from Deepgram

Between 15:17 and 15:45 UTC on October 29, an issue with authentication services at one of our US datacenters caused some API requests and Voice Agent sessions to fail with 5xx errors, and some transcription callbacks sent from that datacenter to carry an invalid Dg-Token header. A fix was deployed at 15:45 UTC and error rates returned to normal. This incident is resolved. All systems are operational.

29 Oct 2026, 16:12 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 18 h 59 min

    Elevated 5xx Errors

  2. , resolved after 10 min

    Elevated API errors

  3. , resolved after 23 h 7 min

    [Deepgram API] Elevated Batch Error Rates: 400 error code responses

  4. , resolved

    Outbound networking issues affecting STT, TTS streaming and batch service

  5. , resolved after 3 h 39 min

    [Deepgram API] Elevated Batch and Streaming STT Error Rates

Other recent Deepgram incidents

  1. Elevated Latency and Errors for Batch STT

  2. Elevated 503 errors for bath Flux TTS requests

  3. Elevated 503 errors for Aura-2 TTS

  4. Elevated error rates for Flux TTS

  5. Elevated errors for Flux TTS

  6. Elevated errors for Flux TTS

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

  8. Elevated latency on Flux STT (US)

All recorded Deepgram incidents