Companies / Deepgram / incidents

Deepgram: Elevated Connection Errors

Affected components: Batch APIDeepgram Public API (api.deepgram.com) - Batch APIDeepgram Public API (api.deepgram.com) - Streaming APIStreaming API

Timeline of updates

1. monitoring2026-01-28 22:10 UTC

   We saw elevated connection errors from 19:12 to 19:19 UTC, and 20:10 to 20:31 UTC. We're no longer seeing spikes in errors, but we're continuing to monitor the situation.

2. investigating2026-01-29 21:18 UTC

   We're observing elevated connection error rates at the moment, and we're actively investigating the issue.

3. investigating2026-01-29 21:19 UTC

   We are continuing to investigate this issue.

4. investigating2026-01-30 17:04 UTC

   We're currently seeing elevated response time, as well as increased 429 errors for batch STT. We're actively working on mitigating the issue.

5. investigating2026-02-02 17:52 UTC

   We are continuing to investigate this issue.

6. monitoring2026-02-03 01:16 UTC

   A fix has been implemented and we are monitoring the results.

7. monitoring2026-02-04 23:21 UTC

   The implemented fixes have resulted in stable systems since 2026-02-03 17:35 UTC. We are continuing to monitor carefully. The issue primarily impacted STT batch services, with some impact on STT streaming. Specifically, response times and 429 errors increased for batch, and a percentage of connection errors occurred for both batch and streaming.

8. resolved2026-02-05 18:56 UTC

   This incident has been resolved.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Deepgram profile · Recent Deepgram incidents · Markdown · JSON