Live

[Deepgram US API] Intermittent connection timeouts

0

Deepgram reported intermittent connection timeouts on the US STT Batch, STT Streaming, TTS Batch, and TTS Streaming APIs. Deepgram reports that the incident is resolved. It lasted about 64 minutes.

State

Resolved

Started

Lasted

1 h 4 min

Worst impact

Degraded

Timeline

3 updates
07:0007:1607:3207:4708:03
NoticeUpdate postedTimes in UTC

Resolved

1 h 4 min 100%

Updates

Times in UTC

As posted by Deepgram

Monitoring

A fix has been implemented and we are monitoring the results.

Investigating

We are currently investigating this issue.

Resolved

This incident has been resolved.

Affected components

8
STT Batch APISTT Streaming APITTS Batch APITTS Streaming APIDeepgram Global API (api.deepgram.com) - STT Batch APIDeepgram Global API (api.deepgram.com) - STT Streaming APIDeepgram Global API (api.deepgram.com) - TTS Batch APIDeepgram Global API (api.deepgram.com) - TTS Streaming API

Deepgram in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

21

Days with an incident

19

Median duration

1 h 4 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

18 h 59 min
median 1 h 4 min
90 days agoToday

Other Deepgram incidents

All incidents

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane