Deepgram Status

Resolved: This incident has been resolved. We will share an RCA of this incident.

Monitoring: 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.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are continuing to investigate this issue.

Investigating: 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: We are continuing to investigate this issue.

Investigating: We're observing elevated connection error rates at the moment, and we're actively investigating the issue.

Monitoring: 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.

Resolved: This incident has been resolved. We will share an RCA of this incident.

Monitoring: 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.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are continuing to investigate this issue.

Investigating: 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: We are continuing to investigate this issue.

Investigating: We're observing elevated connection error rates at the moment, and we're actively investigating the issue.

Monitoring: 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.

Resolved: The incident has been resolved. The downstream provider's status page indicates the issues were resolved at 9:56 PT / 17:56 UTC

Monitoring: We are continuing to monitor for any further issues with the downstream provider.

Monitoring: Failures have reduced since 15:55UTC, we are monitoring the downstream provider's status page.

Identified: We are currently seeing elevated error rates from Anthropic models. To avoid downtime, please define multiple LLM providers (https://developers.deepgram.com/docs/voice-agent-llm-models#using-multiple-llm-providers) in your Voice Agent configuration, including at least one non-Anthropic think provider.

Resolved: The downstream provider indicated the issue was resolved. There was an outage between 16:20 UTC / 8:20 PT and 16:55 UTC / 8:55 PT

Identified: We are currently seeing elevated error rates from Anthropic models. To avoid downtime, please define multiple LLM providers (https://developers.deepgram.com/docs/voice-agent-llm-models#using-multiple-llm-providers) in your Voice Agent configuration, including at least one non-Anthropic think provider. The incident started at 16:34 UTC

Resolved: The incident has been resolved. The downstream provider's status page indicates the issues were resolved at 9:56 PT / 17:56 UTC

Monitoring: We are continuing to monitor for any further issues with the downstream provider.

Monitoring: Failures have reduced since 15:55UTC, we are monitoring the downstream provider's status page.

Identified: We are currently seeing elevated error rates from Anthropic models. To avoid downtime, please define multiple LLM providers (https://developers.deepgram.com/docs/voice-agent-llm-models#using-multiple-llm-providers) in your Voice Agent configuration, including at least one non-Anthropic think provider.

Resolved: The downstream provider indicated the issue was resolved. There was an outage between 16:20 UTC / 8:20 PT and 16:55 UTC / 8:55 PT

Identified: We are currently seeing elevated error rates from Anthropic models. To avoid downtime, please define multiple LLM providers (https://developers.deepgram.com/docs/voice-agent-llm-models#using-multiple-llm-providers) in your Voice Agent configuration, including at least one non-Anthropic think provider. The incident started at 16:34 UTC