- Level
- confirmed
- Worst impact
- Degraded
- Components
- TTS API
- Regions
- au, eu, in
- Down Index
- 33of 100
What to do
Check whether you use Deepgram TTS API in au, eu, in. 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 4h it lasted.
Anything that failed between 2026-09-25 09:45 UTC and 2026-09-25 13:44 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
We are investigating elevated Flux TTS 1011 NET-1000 error rate in Deepgram global endpoint (api.deepgram.com). Regional endpoints (EU, India, Australia) are unaffected.
provider
- resolved
This issue 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-3895acc03c
Is Deepgram still down?
No, this incident was resolved 2026-09-25 13:44 UTC. For Deepgram's live state, see https://down.guide/deepgram.
How long did it last?
4h, from 2026-09-25 09:45 UTC to 2026-09-25 13:44 UTC, by the times Deepgram posted.
What was affected?
Deepgram named TTS API in au, eu, in.
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.