Skip to main content
Deepgram

Elevated 503 errors for Aura-2 TTS

Degraded Lasted 11m · started · Deepgram's page

Level
confirmed
Worst impact
Degraded
Components
TTS API
Down Index
16of 100

What to do

  • Check whether you use Deepgram TTS API. 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 11m it lasted.

    Anything that failed between 2026-10-13 17:58 UTC and 2026-10-13 18:09 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

    We're investigating an issue where some Aura-2 requests failed with HTTP 503 error.

    provider

  2. resolved

    This issue 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-2390437e2b

Is Deepgram still down?

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

How long did it last?

11m, from 2026-10-13 17:58 UTC to 2026-10-13 18:09 UTC, by the times Deepgram posted.

What was affected?

Deepgram named TTS API.

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.