- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu
What to do
Check whether you use Deepgram in eu. 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 18:01 UTC and 2026-08-25 07: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
Resolved Between 07:13 and 09:00 UTC, flux-general-multi Speech-to-Text requests on api.eu.deepgram.com failed shortly after the WebSocket connection was established, returning an internal server error on the first audio and closing the connection. Affected clients saw abnormal closures and reconnect loops. A low rate of residual failures continued until 11:30 UTC. This has been fully investigated, mitigated and resolved, service has fully recovered.
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-e0a0dfa368
Is Deepgram still down?
No, this incident was resolved 2026-08-25 07:00 UTC. For Deepgram's live state, see https://down.guide/deepgram.
How long did it last?
0m, from 2026-08-25 18:01 UTC to 2026-08-25 07:00 UTC, by the times Deepgram posted.
What was affected?
Deepgram named in eu.
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.