- Level
- confirmed
- Worst impact
- Degraded
- Components
- Batch API, Streaming API
- Down Index
- 23of 100
What to do
Check whether you use Deepgram Batch API, Streaming 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 3h 40m it lasted.
Anything that failed between 2026-08-04 14:30 UTC and 2026-08-04 18:10 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 3
- investigating
We are currently investigating an issue where batch and streaming STT requests have degraded performance.
provider
- monitoring
An ISP network failure resulted in poor performance along one network path, resulting in degraded performance that primarily affected STT traffic. All network traffic is now routed through a high quality network path and services have recovered. We are actively monitoring.
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-57bea6c452
Is Deepgram still down?
No, this incident was resolved 2026-08-04 18:10 UTC. For Deepgram's live state, see https://down.guide/deepgram.
How long did it last?
3h 40m, from 2026-08-04 14:30 UTC to 2026-08-04 18:10 UTC, by the times Deepgram posted.
What was affected?
Deepgram named Batch API, Streaming 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.