rewindex

CompaniesDeepgramIncidents

Deepgram: [Deepgram API] Elevated Streaming Response Times

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.deepgram.com (opens in new tab)

Timeline of updates

  1. resolved

    The Deepgram API had a small percentage of streaming requests experience abnormally high response latency on June 12, 2024 from 16:53 UTC to 21:38 UTC. The root cause was identified to be part of a deployment rollout in our data-centers. The deployment was rolled back, at which point stream latency returned to baseline levels.

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 2024-06-12 16:53 UTC, resolved after 0 min, 1 update(s).

Title
[Deepgram API] Elevated Streaming Response Times
Vendor
Deepgram
Date
URL
https://rewindex.com/company/deepgram/incidents/77gkl97fm8jc

Deepgram profileRecent Deepgram incidentsAll outages on June 12, 2024Deepgram in June 2024MarkdownJSON