- Level
- confirmed
- Worst impact
- Degraded
- Components
- Batch API
- Down Index
- 24of 100
What to do
Check whether you use Deepgram Batch API. 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 6h 13m it lasted.
Anything that failed between 2026-06-17 13:35 UTC and 2026-06-17 19:47 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
- identified
Between the hours of 13:35 UTC - 19:47 UTC we noticed an increase in 400 errors returned on PreRecorded STT requests where the payload was a URL. They were transient errors, retrying the request was the recommended course of action and would typically result in a successful transcription.
provider
- resolved
The issue was resolved at 19:47 UTC.
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-32b9db8534
Is Deepgram still down?
No, this incident was resolved 2026-06-17 19:47 UTC. For Deepgram's live state, see https://down.guide/deepgram.
How long did it last?
6h 13m, from 2026-06-17 13:35 UTC to 2026-06-17 19:47 UTC, by the times Deepgram posted.
What was affected?
Deepgram named Batch API.
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.