outages.live
Live

Deepgram

Deepgram is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

17

Days with an incident

15

Median duration

1 h 27 min

Longest incident

18 h 59 min

Components

13

Deepgram Public API (api.deepgram.com)

Batch API Operational
90 days ago5 days with an incidentToday
Streaming API Operational
90 days ago5 days with an incidentToday
TTS API Operational
90 days ago11 days with an incidentToday
Voice Agent API Operational
90 days ago4 days with an incidentToday
Voice Agent API: Downstream Providers Operational
90 days ago3 days with an incidentToday
DG Whisper Cloud Operational
90 days ago3 days with an incidentToday

Documentation

Developer Documentation Operational
90 days agoNo incidentsToday
Deepgram Website Operational
90 days agoNo incidentsToday

On-Premise

License Validation Operational
90 days agoNo incidentsToday
Usage API Operational
90 days agoNo incidentsToday

Developer Console / Management APIs

Developer Console Operational
90 days ago1 day with an incidentToday
API Playground Operational
90 days agoNo incidentsToday
Management APIs Operational
90 days ago2 days with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 29, 2026

Duration55 min15:17 to 16:12Elevated errors from authentication services at one datacenterDegraded

Between 15:17 and 15:45 UTC on October 29, an issue with authentication services at one of our US datacenters caused some API requests and Voice Agent sessions to fail with 5xx errors, and some transcription callbacks sent from that datacenter to carry an invalid Dg-Token header. A fix was deployed at 15:45 UTC and error rates returned to normal. This incident is resolved. All systems are operational.

Oct 22, 2026

Duration2 h 25 min19:27 to 21:53Elevated Latency and Errors for Batch STTDegraded

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.

Duration18 h 59 min16:00 to 11:00Elevated 5xx ErrorsPartial outage

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.

Oct 14, 2026

Duration1 h 31 min19:29 to 21:00Elevated 503 errors for bath Flux TTS requestsDegraded

This issue has been resolved.

Oct 13, 2026

Duration11 min17:58 to 18:09Elevated 503 errors for Aura-2 TTSDegraded

This issue has been resolved.

Oct 8, 2026

Duration1 h 27 min02:58 to 04:25Elevated error rates for Flux TTSDegraded

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.

Oct 5, 2026

Duration2 h09:55 to 11:55Elevated errors for Flux TTSDegraded

This incident has been resolved.

Oct 3, 2026

Duration2 h 1 min15:52 to 17:52Elevated errors for Flux TTSDegraded

This incident has been resolved.

Sep 30, 2026

Duration10 min19:29 to 19:39Elevated API errorsDegraded

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.

Sep 28, 2026

Duration1 min17:53 to 17:53Elevated Latency and Errors for Batch STT (US)Degraded

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.

Duration4 min17:04 to 17:07Elevated latency on Flux STT (US)Degraded

This incident has been resolved.

Sep 25, 2026

Duration4 h09:45 to 13:44Elevated Flux TTS 1011 Error RateDegraded

This issue has been resolved.

Sep 22, 2026

Duration40 min12:10 to 12:50Aura-2 TTS Elevated Error Rates for English VoicesPartial outage

The issue has been resolved.

Sep 2, 2026

Duration3 h 6 min20:22 to 23:28ISP Backbone DegradationDegraded

The upstream ISP failure has been mitigated by rerouting all traffic around that provider.

Follow Deepgram

Your coding agent knows when Deepgram is down, and tells you when a failure is theirs, not yours. You can also get Deepgram incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "deepgram" and tell me if Deepgram has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=deepgram
Slack
/feed subscribe https://outages.live/feed.xml?providers=deepgram

Go from tracking outages to fixing production issues with Polylane.

Try Polylane