Skip to main content
Deepgram

Issues with downstream LLM provider in Voice Agent API

Degraded Lasted 20h 30m · started · Deepgram's page

Level
confirmed
Worst impact
Degraded
Components
Voice Agent API, Voice Agent API: Downstream Providers
Down Index
26of 100

What to do

  • Check whether you use Deepgram Voice Agent API, 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 20h 30m it lasted.

    Anything that failed between 2026-02-23 17:58 UTC and 2026-02-24 14: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

  1. identified

    There is an ongoing Anthropic outage that is affecting our Voice Agent. 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. The incident started at Feb 17, 2026 - 20:15 UTC

    provider

  2. resolved

    The upstream Anthropic incident affecting Claude models has been resolved and error rates have returned to normal. Voice Agent functionality should now be operating as expected.

    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-c154ab455f

Is Deepgram still down?

No, this incident was resolved 2026-02-24 14:28 UTC. For Deepgram's live state, see https://down.guide/deepgram.

How long did it last?

20h 30m, from 2026-02-23 17:58 UTC to 2026-02-24 14:28 UTC, by the times Deepgram posted.

What was affected?

Deepgram named Voice Agent API, 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.