Looking for an update now? Check the current status, or follow Deepgram for future changes.
91.2%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
96.7%
30
1
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.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
A fix has been implemented and we are monitoring the results.
investigating
We are investigating elevated error rates for some Flux Text-to-Speech streaming requests in the US, beginning around 09:55 UTC. Affected users may see connections close unexpectedly with a 1011 / NET-0000 error.
The issue has been identified and a fix is being implemented.
investigating
We are investigating elevated error rates for some Flux Text-to-Speech streaming requests in the US, beginning around 15:52 UTC. Affected users may see connections close unexpectedly with a 1011 / NET-0000 error.
Cogent is experiencing a backbone networking issue in LA, due to two fiber cuts. This is likely impacting a large majority of traffic flowing to the east-coast, we're looking into possible mitigations and Cogent has engineers actively working on it. https://ecogent.cogentco.com/network-status
Legacy Incident Archive
17 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Elevated 5XX Error Rate for v1/auth/grant
minorSource not attested
Last archived state: resolved
View archived record details
Developer ConsoleManagement 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
minorSource not attested
Last archived state: resolved
View archived record details
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.
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
Source not attested
Last archived state: resolved
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
investigating
Flux STT experienced elevated WebSocket streaming errors between 15:56 UTC and 18:20 UTC.
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
minorSource not attested
Last archived state: resolved
View archived record details
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...
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
Source not attested
Last archived state: resolved
View archived record details
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.
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.
