- Level
- confirmed
- Worst impact
- Degraded
- Components
- Batch API, Streaming API, TTS API, Voice Agent API
- Regions
- us
- Down Index
- 19of 100
What to do
Check whether you use Deepgram Batch API, Streaming API, TTS API, Voice Agent API 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 10m it lasted.
Anything that failed between 2026-09-30 19:29 UTC and 2026-09-30 19:39 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
- investigating
We are investigating elevated error rates on API requests to US endpoints. Some requests and connections are failing with HTTP 500 errors or timing out.
provider
- resolved
Between 19:29 and 19:39 UTC, some API requests failed with HTTP 500 errors or timed out. This happened in two short bursts of about 1-2 minutes each, during a planned update to our authentication service. Services have recovered automatically and this issue is resolved.
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-189f0711d9
Is Deepgram still down?
No, this incident was resolved 2026-09-30 19:39 UTC. For Deepgram's live state, see https://down.guide/deepgram.
How long did it last?
10m, from 2026-09-30 19:29 UTC to 2026-09-30 19:39 UTC, by the times Deepgram posted.
What was affected?
Deepgram named Batch API, Streaming API, TTS API, Voice Agent API 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.