checked Oct 23, 2026 7:42 PM UTC · Deepgram's official status page
Deepgram is up and running.
All components operational
Statusfield watches Deepgram alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.
12 reports published by Deepgram in the last 30 days
When Deepgram breaks, it is typically resolved in 18h 27m — median across 1 resolved incidents over 30 days.
resolvedOct 22 · 21:53 UTC
Between 19:27 and 21:53 UTC on October 22, some pre-recorded (batch) requests intermittently had elevated latency, and some timed out. This incident is resolved. All systems are operational.
Reported by Deepgram on their status page.
resolvedOct 23 · 11:00 UTC
Between 16:00 and 17:09 UTC on October 22, some API requests returned 5xx errors because of an issue with authentication services at one of our datacenters. This incident is resolved. All systems are operational.
Reported by Deepgram on their status page.
resolvedOct 14 · 21:00 UTC
This issue has been resolved.
Reported by Deepgram on their status page.
resolvedOct 13 · 18:09 UTC
This issue has been resolved.
Reported by Deepgram on their status page.
resolvedOct 8 · 04:25 UTC
We experienced 2 bursts of elevated error rates between 02:58 - 03:16 UTC and 03:53 - 04:18 UTC. The issue is now resolved.
Reported by Deepgram on their status page.
resolvedOct 5 · 11:55 UTC
This incident has been resolved.
Reported by Deepgram on their status page.
resolvedOct 3 · 17:52 UTC
This incident has been resolved.
Reported by Deepgram on their status page.
resolvedSep 30 · 19:39 UTC
Between 19:29 and 19:39 UTC, some API requests failed with HTTP 500 errors or timed out. This happened in two short bursts of about 1-2 minutes each, during a planned update to our authentication service. Services have recovered automatically and this issue is resolved.
Reported by Deepgram on their status page.
resolvedSep 28 · 17:53 UTC
An issue affecting some of our pre-recorded transcription servers slowed request processing. As requests took longer to complete, some customers saw elevated latency or received 429 errors. We identified and mitigated the issue, service has returned to normal.
Reported by Deepgram on their status page.
resolvedSep 28 · 17:07 UTC
This incident has been resolved.
Reported by Deepgram on their status page.
resolvedSep 28 · 17:00 UTC
Elevated latency on Flux STT (US regions). Between 17:04 and 17:07 UTC, a small share of Flux STT connections in some US regions saw delayed transcripts and some disconnects. This issue has been resolved and service has returned to normal.
Reported by Deepgram on their status page.
resolvedSep 25 · 13:44 UTC
This issue has been resolved.
Reported by Deepgram on their status page.
