- Level
- confirmed
- Worst impact
- Degraded
- Components
- Batch API
- Down Index
- 21of 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 1h 49m it lasted.
Anything that failed between 2026-05-12 16:18 UTC and 2026-05-12 18:07 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
During the affected time period, some English batch speech-to-text requests intermittently returned 404 Not Found HTTP errors. This issue was limited to requests that met both of the following criteria: - Utilized English batch STT models (including both monolingual English and multilingual models that support English transcription) - Had Smart Format, Entity Detection, or Redaction features enabled.
provider
- resolved
This incident has been 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-6c5917e712
Is Deepgram still down?
No, this incident was resolved 2026-05-12 18:07 UTC. For Deepgram's live state, see https://down.guide/deepgram.
How long did it last?
1h 49m, from 2026-05-12 16:18 UTC to 2026-05-12 18:07 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.