Deepgram: Elevated Latency and Errors for Batch STT
Affected components: - Batch APIDeepgram Public API - api.deepgram.com
Timeline of updates
- investigating
We are currently investigating elevated latency and 5xx error rates returned from batch requests to our API platform.
- resolved
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.
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-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
f072fafa33b31787…
Impact, status and times are the vendor’s own, as last archived. View on status.deepgram.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Deepgram, started 2026-10-22 21:53 UTC, resolved after 0 min, 2 update(s).
- Title
- Elevated Latency and Errors for Batch STT
- Vendor
- Deepgram
- Date
- URL
- https://rewindex.com/company/deepgram/incidents/vxsw6p7f8wcw
Deepgram profileRecent Deepgram incidentsAll outages on October 22, 2026Deepgram in October 2026MarkdownJSON