- 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 1d 3h it lasted.
Anything that failed between 2026-02-12 17:47 UTC and 2026-02-13 21:28 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 currently seeing elevated error rates from OpenAI models. 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, including at least one non-OpenAI think provider. The incident started at 17:47 UTC
provider
- resolved
The 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-2278c9f7c4
Is Deepgram still down?
No, this incident was resolved 2026-02-13 21:28 UTC. For Deepgram's live state, see https://down.guide/deepgram.
How long did it last?
1d 3h, from 2026-02-12 17:47 UTC to 2026-02-13 21:28 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.