Deepgram Voice AI incident

Elevated Connection Errors

Minor Resolved View vendor source →

Deepgram Voice AI experienced a minor incident on January 28, 2026 affecting Batch API and Streaming API, lasting 7d 20h. The incident has been resolved; the full update timeline is below.

Started
Jan 28, 2026, 10:10 PM UTC
Resolved
Feb 05, 2026, 06:56 PM UTC
Duration
7d 20h
Detected by Pingoru
Jan 28, 2026, 10:10 PM UTC

Affected components

Batch APIStreaming API

Update timeline

  1. monitoring Jan 28, 2026, 10:10 PM 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. investigating Jan 29, 2026, 09:18 PM UTC

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

  3. investigating Jan 29, 2026, 09:19 PM UTC

    We are continuing to investigate this issue.

  4. investigating Jan 30, 2026, 05:04 PM 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. investigating Feb 02, 2026, 05:52 PM UTC

    We are continuing to investigate this issue.

  6. monitoring Feb 03, 2026, 01:16 AM UTC

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

  7. monitoring Feb 04, 2026, 11:21 PM 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. resolved Feb 05, 2026, 06:56 PM UTC

    This incident has been resolved.