Outage recap · Deepgram

Deepgram outage — January 28, 2026

On January 28, 2026, Deepgram had a reported incident on Deepgram's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Elevated Connection Errors

minor
Started
Jan 28, 5:10 PM EST
Resolved
Feb 5, 1:56 PM EST
Duration
188h 46m

Deepgram's updates (8)

  1. monitoring · Jan 28, 5:10 PM EST

    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, 4:18 PM EST

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

  3. investigating · Jan 29, 4:19 PM EST

    We are continuing to investigate this issue.

  4. investigating · Jan 30, 12:04 PM EST

    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 2, 12:52 PM EST

    We are continuing to investigate this issue.

  6. monitoring · Feb 2, 8:16 PM EST

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

  7. monitoring · Feb 4, 6:21 PM EST

    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 5, 1:56 PM EST

    This incident has been resolved.

Updates are Deepgram's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

AIDownCheck is not affiliated with Deepgram. This recap summarizes incidents published on Deepgram's official status page.