- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Deepgram. 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-08-25 16:41 UTC and 2026-08-24 23:00 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 1
- resolved
Between 23:18 and 23:45 UTC, a portion of streaming STT connection requests failed with 5XX errors and timeouts. While rolling out a new data center, we detected streaming errors and immediately removed it from rotation. Traffic to the new site had been intentionally limited to a small percentage while we verified the rollout, which limited the number of affected requests. This is now fully 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-027f7e03d9
Is Deepgram still down?
No, this incident was resolved 2026-08-24 23:00 UTC. For Deepgram's live state, see https://down.guide/deepgram.
How long did it last?
0m, from 2026-08-25 16:41 UTC to 2026-08-24 23:00 UTC, by the times Deepgram posted.
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.