Live / Deepgram / Incident
Deepgram: Elevated 5xx Errors
Deepgram · deepgram.comMajor incidentResolved2026-10-23 11:00 UTC
Public — what happened
Summary
Deepgram reported a major incident involving a higher-than-normal rate of server errors (5xx) affecting its authentication services at one of its datacenters. The company said it began investigating at 17:06 UTC on 2026-10-22, and by 17:29 UTC it said it had identified the issue and was monitoring a solution. The incident was marked resolved at 11:00 on 2026-10-23. Deepgram did not say in its updates what caused the problem or how many customers were affected.
Affected
Batch API, Streaming API, TTS API, Voice Agent API, Voice Agent API: Downstream Providers, DG Whisper Cloud
Timeline
- Started — 2026-10-22 17:06 UTC
- Investigating — 2026-10-22 17:06 UTC (2 updates)
- Monitoring — 2026-10-22 17:29 UTC
- Resolved — 2026-10-23 11:00 UTC · 17h 53m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Deepgram against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Deepgram: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Deepgram report →
More from Deepgram
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.