outages.live
Live
DeepgramIncident ·

Flux TTS high latency and websocket disconnects

ResolvedOfficial update
0

Deepgram Flux TTS had high latency and websocket disconnects on the TTS API and the Deepgram Public API. Deepgram reported the incident as resolved after 7 minutes.

State

Resolved

Started

Lasted

7 min

Worst impact

Partial outage

Timeline

2 updates
13:5313:5413:5613:5814:00
Partial outageUpdate postedTimes in UTC

Investigating

7 min 100%

Updates

Times in UTC

As posted by Deepgram

Resolved
Investigating

We are currently investigating this issue.

Affected components

2
TTS APIDeepgram Public API (api.deepgram.com) - TTS API

Deepgram in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

19

Days with an incident

18

Median duration

1 h 9 min

This incident

89% shorter than 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 9 min
90 days agoToday

Other Deepgram incidents

All incidents

Deepgram·Flux TTS high latency and websocket disconnects

Flux TTS disconnects occurred between 03:10 - 03:20, with high Flux TTS latency leading up to 03:10. The issue is now resolved.

Resolved

Deepgram·Elevated errors for Flux streaming STT and Voice Agent sessions

Deepgram Flux streaming speech-to-text requests failed at the US endpoint. Voice Agent sessions with a Flux listen model also failed to start. The incident is resolved and lasted 6 hours and 33 minutes.

Resolved

Deepgram·Elevated errors from authentication services at one datacenter

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.

Resolved

Deepgram·Elevated Latency and Errors for Batch STT

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.

Resolved

Deepgram·Elevated 5xx Errors

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.

Resolved

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