Outage recap · Deepgram

Deepgram outage — November 18, 2026

On November 18, 2026, Deepgram had 2 reported incidents on Deepgram's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

[Deepgram US API] Intermittent connection timeouts

minor
Started
Nov 18, 2:00 AM EST
Resolved
Nov 18, 3:03 AM EST
Duration
1h 4m

Deepgram's updates (3)

  1. investigating · Nov 18, 2:00 AM EST

    We are currently investigating this issue.

  2. resolved · Nov 18, 3:03 AM EST

    This incident has been resolved.

  3. monitoring · Nov 18, 4:04 AM EST

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

What our checks recorded

We checked Deepgram 13 times from Deepgram's start time to its resolution, once every five minutes. Every one of them reached Deepgram's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 711 ms, against 581 ms over the 24 hours before. Deepgram posted the incident at Nov 18, 2:00 AM EST.

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

[Deepgram US API] Intermittent connection timeouts

minor
Started
Nov 18, 11:26 AM EST
Resolved
Nov 18, 5:37 PM EST
Duration
6h 12m

Deepgram's updates (7)

  1. investigating · Nov 18, 11:26 AM EST

    We are currently investigating this issue.

  2. monitoring · Nov 18, 12:28 PM EST

    A network connectivity issue at one of our US data centers caused in-progress streaming sessions to disconnect, and some new requests received 503 errors while traffic was rerouted to our other data centers. Since then, some customers may have seen intermittent errors and elevated latency while traffic rebalanced across our data centers.

  3. monitoring · Nov 18, 12:38 PM EST

    We are continuing to monitor for any further issues.

  4. investigating · Nov 18, 12:56 PM EST

    We are currently investigating this issue.

  5. investigating · Nov 18, 1:01 PM EST

    We are continuing to investigate this issue.

  6. monitoring · Nov 18, 2:23 PM EST

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

  7. resolved · Nov 18, 5:37 PM EST

    This incident has been resolved.

What our checks recorded

We checked Deepgram 74 times from Deepgram's start time to its resolution, once every five minutes. Every one of them reached Deepgram's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 657 ms, against 600 ms over the 24 hours before. Deepgram posted the incident at Nov 18, 11:26 AM EST.

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.