Skip to main content
Deepgram

Intermittent Connectivity Issues Due to AWS US-WEST-2 Infrastructure Event

Degraded Lasted 4m · started · Deepgram's page

Level
confirmed
Worst impact
Degraded
Regions
us, us-west-2
Down Index
20of 100

What to do

  • Check whether you use Deepgram in us, us-west-2. 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 4m it lasted.

    Anything that failed between 2026-07-24 13:18 UTC and 2026-07-24 13:22 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. investigating

    Between approximately 10:55 and 12:00 UTC on July 24, an upstream infrastructure issue in AWS's US-WEST-2 region caused intermittent connectivity problems that may have affected Deepgram services and customer infrastructure — including elevated errors, connection timeouts, and failures fetching remotely hosted media for some requests. The underlying cause was an AWS networking issue affecting routing to the US-WEST-2 region. AWS applied mitigations and fully restored connectivity by ~12:00 UTC. We have confirmed recovery and are continuing to monitor. Details on the underlying AWS event are available on the AWS Health status page: https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-west-2::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_83A36_24C89B493A6

    provider

  2. 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-e9adb3ad4f

Is Deepgram still down?

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

How long did it last?

4m, from 2026-07-24 13:18 UTC to 2026-07-24 13:22 UTC, by the times Deepgram posted.

What was affected?

Deepgram named in us, us-west-2.

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.