- Level
- confirmed
- Worst impact
- Partial outage
- Components
- TTS API
- Down Index
- 28of 100
What to do
Check whether you use Deepgram 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 40m it lasted.
Anything that failed between 2026-09-22 12:10 UTC and 2026-09-22 12:50 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.
Root cause
We are working to identify the cause and restore full service availability.Read the postmortem
Updates from Deepgram 2
- investigating
We are investigating elevated 503 Service Unavailable errors affecting some Aura-2 TTS requests for English voices. We are working to identify the cause and restore full service availability.
provider
- resolved
The 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-59ea5841bb
Is Deepgram still down?
No, this incident was resolved 2026-09-22 12:50 UTC. For Deepgram's live state, see https://down.guide/deepgram.
How long did it last?
40m, from 2026-09-22 12:10 UTC to 2026-09-22 12:50 UTC, by the times Deepgram posted.
What was affected?
Deepgram named TTS API.
What caused it?
Deepgram wrote: "We are working to identify the cause and restore full service availability." The postmortem: https://stspg.io/1mbrwsmd1034
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.