Elevated errors for Flux streaming STT and Voice Agent sessions
none- Started
- Nov 5, 1:42 PM EST
- Resolved
- Nov 5, 8:14 PM EST
- Duration
- 6h 33m
Deepgram's updates (3)
- investigating · Nov 5, 1:42 PM EST
We are currently investigating elevated errors for Flux streaming speech-to-text requests at our US endpoint. Voice Agent sessions configured with a Flux listen model may fail to start with a FAILED_TO_START_LISTENING error. Other models are not affected.
- monitoring · Nov 5, 1:51 PM EST
A fix has been implemented and we are monitoring the results.
- resolved · Nov 5, 8:14 PM EST
This incident has been resolved.
What our checks recorded
We checked Deepgram 78 times from Deepgram's start time to its resolution, once every five minutes. Every one of them reached Deepgram's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 638 ms, against 583 ms over the 24 hours before. Deepgram posted the incident at Nov 5, 1:42 PM EST.
Updates are Deepgram's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗