- Level
- confirmed
- Worst impact
- Degraded
- Components
- Batch API, Streaming API, TTS API
- Down Index
- 28of 100
What to do
Check whether you use Deepgram Batch API, Streaming API, TTS 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 23h 8m it lasted.
Anything that failed between 2026-07-28 14:00 UTC and 2026-07-29 13:08 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 7
- investigating
We are currently investigating an issue where some batch requests are returning 400 errors due to remote content download errors. Retrying the request one or more times often succeeds.
provider
- investigating
We are continuing to investigate this issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- investigating
We are continuing to investigate an issue. STT batch requests may have returned 5xx errors, and some STT websockets may have experienced high latency, starting at 16:03 UTC.
provider
- monitoring
A fix has been implemented and traffic has returned to normal. We are monitoring the results.
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-e5a9867e3c
Is Deepgram still down?
No, this incident was resolved 2026-07-29 13:08 UTC. For Deepgram's live state, see https://down.guide/deepgram.
How long did it last?
23h 8m, from 2026-07-28 14:00 UTC to 2026-07-29 13:08 UTC, by the times Deepgram posted.
What was affected?
Deepgram named Batch API, Streaming API, TTS 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.