Skip to main content
Deepgram

Elevated errors from authentication services at one datacenter

Degraded Lasted 55m · started · Deepgram's page

Level
confirmed
Worst impact
Degraded
Components
Batch API, Streaming API, TTS API, Voice Agent API, Voice Agent API: Downstream Providers, DG Whisper Cloud
Regions
us

What to do

  • Check whether you use Deepgram Batch API, Streaming API, TTS API, Voice Agent API and 2 more in us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 55m it lasted.

    Anything that failed between 2026-10-29 15:17 UTC and 2026-10-29 16:12 UTC may need a replay.
  • Subscribe to Deepgram's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=deepgram works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Deepgram 2

  1. investigating

    We are investigating elevated errors with authentication services at one of our US datacenters. Some API requests and Voice Agent sessions routed there may fail with 5xx errors, and some transcription callbacks sent from that datacenter may carry an invalid Dg-Token header.

    provider

  2. resolved

    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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-82af31f2f7

Is Deepgram still down?

No, this incident was resolved 2026-10-29 16:12 UTC. For Deepgram's live state, see https://down.guide/deepgram.

How long did it last?

55m, from 2026-10-29 15:17 UTC to 2026-10-29 16:12 UTC, by the times Deepgram posted.

What was affected?

Deepgram named Batch API, Streaming API, TTS API, Voice Agent API and 2 more in us.

What caused it?

Deepgram hasn't published a root cause. If it does, it shows here.

Where does this come from?

Deepgram's official status page, https://status.deepgram.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.