Elevated errors for Flux TTS
minor- Started
- Oct 3, 11:52 AM EDT
- Resolved
- Oct 3, 1:52 PM EDT
- Duration
- 2h 1m
Deepgram's updates (3)
- investigating · Oct 3, 11:52 AM EDT
We are investigating elevated error rates for some Flux Text-to-Speech streaming requests in the US, beginning around 15:52 UTC. Affected users may see connections close unexpectedly with a 1011 / NET-0000 error.
- identified · Oct 3, 1:46 PM EDT
The issue has been identified and a fix is being implemented.
- resolved · Oct 3, 1:52 PM EDT
This incident has been resolved.
What our checks recorded
We checked Deepgram 24 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 120 ms, against 123 ms over the 24 hours before. Deepgram posted the incident at Oct 3, 11:52 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 ↗