Deepgram: Degraded API Performance
Timeline of updates
- resolved
Between 15:16 and 15:32 UTC on March 25, 2026, we noticed an increased rate of API requests returning errors, including 403, 404, and 504 status codes. The issue has been identified and resolved.
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a0fbaa4980d3056e…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Deepgram, started 2026-03-25 15:16 UTC, resolved after 0 min, 1 update(s).
- Title
- Degraded API Performance
- Vendor
- Deepgram
- Date
- URL
- https://rewindex.com/company/deepgram/incidents/vd9xjx3pkyv6
Deepgram profileRecent Deepgram incidentsAll outages on March 25, 2026Deepgram in March 2026MarkdownJSON