Deepgram: [Deepgram API] Elevated 500 Errors for Redaction on Non-English Audio
Timeline of updates
- resolved
Between March 22 at 20:00 UTC and March 24 at 14:39 UTC, some ASR requests that included redaction for non-English audio returned 500 errors due to an internal configuration issue. This issue affected only redaction requests and did not impact ASR performance for audio without redaction. Service has been fully restored for Deepgram models, and additional safeguards have been implemented to prevent similar incidents in the future.
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: minor) posted by Deepgram, started 2025-03-23 03:00 UTC, resolved after 0 min, 1 update(s).
- Title
- [Deepgram API] Elevated 500 Errors for Redaction on Non-English Audio
- Vendor
- Deepgram
- Date
- URL
- https://rewindex.com/company/deepgram/incidents/23d5kr31rm2f
Deepgram profileRecent Deepgram incidentsAll outages on March 23, 2025Deepgram in March 2025MarkdownJSON