- Level
- confirmed
- Worst impact
- Degraded
- Components
- Voice Agent API: Downstream Providers
- Down Index
- 20of 100
What to do
Check whether you use Deepgram Voice Agent API: Downstream Providers. 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 1h 34m it lasted.
Anything that failed between 2026-07-21 13:45 UTC and 2026-07-21 15:20 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
Starting at 13:45 PM UTC, some Voice Agent sessions using Google/Gemini without a pinned model version received failed responses due to a routing issue introduced in this morning's deploy. Two Gemini models were unaffected; all other providers and products were unaffected. The issue was resolved as of 3:20 PM UTC.
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-647ab75e7f
Is Deepgram still down?
No, this incident was resolved 2026-07-21 15:20 UTC. For Deepgram's live state, see https://down.guide/deepgram.
How long did it last?
1h 34m, from 2026-07-21 13:45 UTC to 2026-07-21 15:20 UTC, by the times Deepgram posted.
What was affected?
Deepgram named Voice Agent API: Downstream Providers.
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.