Deepgram outage, 22 October 2026

Elevated Latency and Errors for Batch STT

Started
Resolved
22 Oct 2026, 21:53 UTC (after 2 h 25 min)
Impact
Minor
Affected
Batch API

Is this still happening?

No. Deepgram marked this incident resolved on 22 Oct 2026, 21:53 UTC, 2 h 25 min after it began.

Right now: Deepgram reports all systems operational. (as of 26 Oct, 03:45 UTC) Live Deepgram status

Last update from Deepgram

Between 19:27 and 21:53 UTC on October 22, some pre-recorded (batch) requests intermittently had elevated latency, and some timed out. This incident is resolved. All systems are operational.

22 Oct 2026, 21:53 UTC

Read the full incident on the official Deepgram status page

Similar Deepgram incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved

    Elevated Latency and Errors for Batch STT (US)

  2. , resolved after 3 h 39 min

    [Deepgram API] Elevated Batch and Streaming STT Error Rates

  3. , resolved after 23 h 7 min

    [Deepgram API] Elevated Batch Error Rates: 400 error code responses

  4. , resolved after 6 h 12 min

    400 errors with PreRecorded STT ("REMOTE_CONTENT_ERROR" / "failed to return valid data") when passing a URL

  5. , resolved

    Outbound networking issues affecting STT, TTS streaming and batch service

Other recent Deepgram incidents

  1. Elevated 5xx Errors

  2. Elevated 503 errors for bath Flux TTS requests

  3. Elevated 503 errors for Aura-2 TTS

  4. Elevated error rates for Flux TTS

  5. Elevated errors for Flux TTS

  6. Elevated errors for Flux TTS

  7. Elevated API errors

  8. Elevated latency on Flux STT (US)

All recorded Deepgram incidents