- Level
- confirmed
- Worst impact
- Degraded
- Components
- Voice Agent API: Downstream Providers
- Down Index
- 25of 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 10h it lasted.
Anything that failed between 2026-06-17 18:00 UTC and 2026-06-18 04: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 4
- investigating
We are currently investigating elevated error rates affecting Voice Agent requests that use Google Gemini models. During this period, some requests to Google models (including gemini-2.5-flash-lite) may fail or time out. Other Voice Agent functionality and non-Google models are not affected. Our team is actively working to identify the cause and restore full service. We will provide an update shortly. To avoid downtime, please define multiple LLM providers (https://developers.deepgram.com/docs/voice-agent-llm-models#using-multiple-llm-providers) in your Voice Agent configuration.
provider
- identified
We have identified the cause of elevated error rates affecting Voice Agent requests that use Google Gemini models. A recent change on Google's side to how API keys operate is causing requests to fail, and our team is rolling out updated credentials to resolve it. Until the update is complete, customers may see intermittent failures for Gemini-model requests — concentrated in the first half of each hour, with most requests succeeding in the second half. Other Voice Agent models are unaffected. We are actively working on the fix and will update when resolved.
provider
- identified
Continuing to monitor; root cause confirmed as the Google API key change.
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-e3ea867680
Is Deepgram still down?
No, this incident was resolved 2026-06-18 04:00 UTC. For Deepgram's live state, see https://down.guide/deepgram.
How long did it last?
10h, from 2026-06-17 18:00 UTC to 2026-06-18 04:00 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.