Deepgram: [Deepgram API] Elevated Streaming STT Error Rates
Timeline of updates
- resolved
Between 23:18 and 23:45 UTC, a portion of streaming STT connection requests failed with 5XX errors and timeouts.
While rolling out a new data center, we detected streaming errors and immediately removed it from rotation. Traffic to the new site had been intentionally limited to a small percentage while we verified the rollout, which limited the number of affected requests. This is now fully resolved.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
c66c66bd1d5d32d3…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Deepgram, started 2026-08-25 16:41 UTC, resolved after -1062 min, 1 update(s).
- Title
- [Deepgram API] Elevated Streaming STT Error Rates
- Vendor
- Deepgram
- Date
- URL
- https://rewindex.com/company/deepgram/incidents/kp3y1k6jbzcy
Deepgram profileRecent Deepgram incidentsAll outages on August 25, 2026Deepgram in August 2026MarkdownJSON