- Level
- confirmed
- Worst impact
- Degraded
- Components
- Batch API
- Regions
- us
What to do
Check whether you use Deepgram Batch 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 0m it lasted.
Anything that failed between 2026-09-28 17:53 UTC and 2026-09-28 17:53 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 latency and 429 errors affecting some pre-recorded (batch) STT requests.
provider
- resolved
An issue affecting some of our pre-recorded transcription servers slowed request processing. As requests took longer to complete, some customers saw elevated latency or received 429 errors. We identified and mitigated the issue, service has returned to normal.
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-ab9a5d245d
Is Deepgram still down?
No, this incident was resolved 2026-09-28 17:53 UTC. For Deepgram's live state, see https://down.guide/deepgram.
How long did it last?
0m, from 2026-09-28 17:53 UTC to 2026-09-28 17:53 UTC, by the times Deepgram posted.
What was affected?
Deepgram named Batch 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.