Elevated errors for Flux TTS
minor- Started
- Oct 5, 7:33 AM EDT
- Resolved
- Oct 5, 7:55 AM EDT
- Duration
- 22 min
Deepgram's updates (3)
- investigating · Oct 5, 5:55 AM EDT
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.
- monitoring · Oct 5, 7:40 AM EDT
A fix has been implemented and we are monitoring the results.
- resolved · Oct 5, 7:55 AM EDT
This incident has been resolved.
What our checks recorded
We checked Deepgram 5 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 117 ms, against 122 ms over the 24 hours before. Deepgram posted the incident at Oct 5, 5:55 AM EDT.
Updates are Deepgram's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗