Deepgram Outage History
Daily status observations, past incidents, and reported issue history for Deepgram.
Checking current status...
90-Day Trend
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 92% | 25 | 2 |
| July 2026 | 87.1% | 31 | 4 |
| June 2026 | 76.7% | 30 | 7 |
| May 2026 | 100% | 5 | 0 |
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Daily Status (Last 91 Days)
May 27
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
Elevated 5XX Error Rate for v1/auth/grant
Started:
Developer Console
Management APIs
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We're seeing elevated error rate for authentication services. We are currently investigating the issue
[Deepgram API] Elevated Batch and Streaming STT Error Rates
Started:
monitoring
An ISP network failure resulted in poor performance along one network path, resulting in degraded performance that primarily affected STT traffic. All network traffic is now routed through a high quality network path and services have recovered. We are actively monitoring.
investigating
We are currently investigating an issue where batch and streaming STT requests have degraded performance.
July 2026
[Deepgram API] Elevated Batch Error Rates: 400 error code responses
Started:
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate an issue where some STT batch, STT streaming, and TTS requests are returning 4xx errors or websocket streams are closing.
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating an issue where some batch requests are returning 400 errors due to remote content download errors. Retrying the request one or more times often succeeds.
Intermittent Connectivity Issues Due to AWS US-WEST-2 Infrastructure Event
Started:
investigating
Between approximately 10:55 and 12:00 UTC on July 24, an upstream infrastructure issue in AWS's US-WEST-2 region caused intermittent connectivity problems that may have affected Deepgram services and customer infrastructure — including elevated errors, connection timeouts, and failures fetching remotely hosted media for some requests.
The underlying cause was an AWS networking issue affecting routing to the US-WEST-2 region. AWS applied mitigations and fully restored connectivity by ~12:00...
Elevated 5XX Errors for Flux STT Requests
Started:
investigating
Flux STT experienced elevated WebSocket streaming errors between 15:56 UTC and 18:20 UTC.
June 2026
Voice Agent third-party provider Instability (Anthropic LLMs)
Started:
monitoring
We are currently observing elevated error rates from our downstream third-party provider, Anthropic. Deepgram infrastructure, including our canaries, remains healthy.
Incident start time: Jun 23, 2026, 14:19 UTC
(Anthropic status updates: https://status.claude.com)
Elevated errors when using Google Gemini models with Voice Agent
Started:
identified
We have identified the cause of elevated error rates affecting Voice Agent requests that use Google Gemini models. A recent change on Google's side to how API keys operate is causing requests to fail, and our team is rolling out updated credentials to resolve it. Until the update is complete, customers may see intermittent failures for Gemini-model requests — concentrated in the first half of each hour, with most requests succeeding in the second half. Other Voice Agent models are unaffecte...
investigating
We are currently investigating elevated error rates affecting Voice Agent requests that use Google Gemini models. During this period, some requests to Google models (including gemini-2.5-flash-lite) may fail or time out. Other Voice Agent functionality and non-Google models are not affected. Our team is actively working to identify the cause and restore full service. We will provide an update shortly.
To avoid downtime, please define multiple LLM providers (https://developers.deepgram.com/do...
Degraded performance — Flux streaming Speech-to-Text
Started:
identified
We identified a degradation affecting a subset of Flux streaming Speech-to-Text sessions, where connections terminated before returning a transcript. We've isolated it to specific degraded hosts and are mitigating.
investigating
Some streaming Speech-to-Text connections on the Flux model established successfully but then terminated a few seconds into the session due to an internal error, before returning a final transcript. Applications relying on final transcripts (e.g. IVR/voice-agent flows) would have seen sessions open with no transcript returned.
May 2026
Degraded API Performance
Started:
monitoring
Some API requests may have experienced increased latency and elevated error rates for approximately 30 minutes starting at 16:40 UTC on May 22, 2026. The issue has been identified and is being resolved.
Voice Agent third-party provider instability (ChatGPT 4o)
Started:
identified
We are currently observing elevated error rates from our downstream third-party provider, OpenAI specifically with the ChatGPT 4o model. Deepgram infrastructure, including our canaries, remains healthy.
April 2026
Voice Agent third-party provider instability (Claude Sonnet 4.5)
Started:
investigating
We are currently observing elevated error rates from our downstream third-party provider, Anthropic specifically with the Claude Sonnet 4.5 model. Deepgram infrastructure, including our canaries, remains healthy.
Voice Agent third-party provider instability (Google Gemini LLMs)
Started:
identified
We are currently observing elevated error rates from our downstream third-party provider, Google Gemini LLMs. Deepgram infrastructure, including our canaries, remains healthy; however, Voice Agent customers using bring-your-own (BYO) Gemini LLMs may experience degraded performance or intermittent failures on LLM think requests.
We are monitoring the situation and tracking the provider’s status at https://aistudio.google.com/status. We will provide further updates as more information become...
Issues with downstream LLM provider in Voice Agent API
Started:
investigating
We are currently seeing elevated error rates from OpenAI models. To avoid downtime, please define multiple LLM providers (https://developers.deepgram.com/docs/voice-agent-llm-models#using-multiple-llm-providers) in your Voice Agent configuration.
Outbound networking issues affecting STT PreRecorded API requests with callbacks, TTS Batch (HTTP) requests with callbacks, and Voice Agent API BYO 3rd party providers (LLM and TTS)
Started:
monitoring
A network infrastructure fix was implemented at 18:15 UTC and the behavior was immediately resolved. We are continuing to monitor carefully.
identified
A networking incident was identified which resulted in failed callbacks on STT PreRecorded API requests and TTS Batch requests. The issue also affected Voice Agent API sessions with LLM and TTS providers. We have identified a fix and are monitoring traffic. The source of the issue is being investigated.
Issues with downstream LLM provider in Voice Agent API
Started:
identified
We are seeing elevated error rates and latency when using NVIDIA Llama Nemotron Super 49B (llama-nemotron-super-49B) as the managed LLM in Voice Agent API. To avoid downtime, please define multiple LLM providers (https://developers.deepgram.com/docs/voice-agent-llm-models#using-multiple-llm-providers) in your Voice Agent configuration.
March 2026
Voice Agent API Degraded Service
Started:
investigating
There is an ongoing OpenAI outage that is affecting our Voice Agent. To avoid downtime, please define multiple LLM providers (https://developers.deepgram.com/docs/voice-agent-llm-models#using-multiple-llm-providers) in your Voice Agent configuration.
Voice Agent API Degraded Performance
Started:
identified
We are continuing to work on a fix for this issue.
identified
There is an ongoing OpenAI outage that is affecting our Voice Agent. To avoid downtime, please define multiple LLM providers (https://developers.deepgram.com/docs/voice-agent-llm-models#using-multiple-llm-providers) in your Voice Agent configuration.