Resolved after 7 days 20 hours, affecting Batch API and Streaming API, on January 28, 2026.
The implemented fixes have resulted in stable systems since 2026-02-03 17:35 UTC. We are continuing to monitor carefully. The issue primarily impacted STT batch services, with some impact on STT streaming. Specifically, response times and 429 errors increased for batch, and a percentage of connection errors occurred for both batch and streaming.
Affected components
Update timeline
- monitoring Jan 28, 2026, 10:10 PM UTC
We saw elevated connection errors from 19:12 to 19:19 UTC, and 20:10 to 20:31 UTC. We're no longer seeing spikes in errors, but we're continuing to monitor the situation.
- investigating Jan 29, 2026, 09:18 PM UTC
We're observing elevated connection error rates at the moment, and we're actively investigating the issue.
- investigating Jan 29, 2026, 09:19 PM UTC
We are continuing to investigate this issue.
- investigating Jan 30, 2026, 05:04 PM UTC
We're currently seeing elevated response time, as well as increased 429 errors for batch STT. We're actively working on mitigating the issue.
- investigating Feb 02, 2026, 05:52 PM UTC
We are continuing to investigate this issue.
- monitoring Feb 03, 2026, 01:16 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Feb 04, 2026, 11:21 PM UTC
The implemented fixes have resulted in stable systems since 2026-02-03 17:35 UTC. We are continuing to monitor carefully. The issue primarily impacted STT batch services, with some impact on STT streaming. Specifically, response times and 429 errors increased for batch, and a percentage of connection errors occurred for both batch and streaming.
- resolved Feb 05, 2026, 06:56 PM UTC
This incident has been resolved.
Your product runs on more than Deepgram Voice AI
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services