Deepgram outage history

We hold 55 Deepgram incidents from Deepgram's status page, the newest from Nov 18, 2026. 55 of the 55 listed carry Deepgram's own update timeline. Each one links to a page with the vendor's updates and what our five-minute checks recorded while it was open.

Uptime & history

Tracking since Jun 22, 2026
Currently up for 23h 53m since the last recorded problem.
Operational · 24h
99.31%
0 incidents · ≈10m degraded
288 checks
Operational · 7d
98.46%
3 incidents · ≈2h 35m degraded
2015 checks
Operational · 30d
99.55%
8 incidents · ≈3h 15m degraded
8638 checks
Operational · since Jun 22, 2026
99.82%
30 incidents · ≈6h 10m degraded
41942 checks

% of our checks that found Deepgram fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.

Recent checks
oldernow
Past incidents

How Deepgram fails

Since Jul 28, 2026, Deepgram's status page has marked 12 Deepgram components as impaired, across 218 of our five-minute readings. Voice Agent API accounts for the most: 32 readings (about 2.7 hours) on 3 days, most recently on Nov 18, 2026. Next is STT Streaming API, with 31 readings on 2 days. We hold 55 Deepgram incidents from Deepgram's status page, the earliest from Jan 28, 2026. Of the 42 that Deepgram closed with an end time, the median lasted 3 h 6 min.

ComponentOutageDegradedMaint.DaysLast
Voice Agent API—32—3Nov 18, 2026
STT Streaming API—31—2Nov 18, 2026
STT Batch API—30—1Nov 18, 2026
Batch API—25—6Oct 29, 2026
TTS API—22—7Nov 10, 2026
Streaming API—20—5Oct 29, 2026
TTS Streaming API—14—2Nov 18, 2026
TTS Batch API—13—1Nov 18, 2026

Incidents by month: Jun 2026: 6 · Jul 2026: 4 · Aug 2026: 5 · Sep 2026: 6 · Oct 2026: 8 · Nov 2026: 5

Counts are five-minute readings of Deepgram's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.

Every recorded incident

November 2026 · 5

October 2026 · 8

September 2026 · 6

August 2026 · 5

July 2026 · 4

March 2026 · 4

February 2026 · 6

January 2026 · 1

Incidents and their updates are Deepgram's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Deepgram.