Deepgram: Streaming connection errors
Timeline of updates
- resolved
A portion of streams connecting to Deepgram from 19:43 to 19:45 UTC resulted in 503 errors due to a deployment that was briefly in an unhealthy state.
From Deepgram’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
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: none) posted by Deepgram, started 2025-04-07 07:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Streaming connection errors
- Vendor
- Deepgram
- Date
- URL
- https://rewindex.com/company/deepgram/incidents/72ld15qt5tmb
Deepgram profileRecent Deepgram incidentsAll outages on April 7, 2025Deepgram in April 2025MarkdownJSON