rewindex

CompaniesDeepgramIncidents

Deepgram: 400 errors with PreRecorded STT ("REMOTE_CONTENT_ERROR" / "failed to return valid data") when passing a URL

MinorStatus: resolvedStarted Resolved (6.2 h)2 updatesstspg.io (opens in new tab)

Affected components: Batch APIDeepgram Public API (api.deepgram.com) - Batch API

Timeline of updates

  1. identified

    Between the hours of 13:35 UTC - 19:47 UTC we noticed an increase in 400 errors returned on PreRecorded STT requests where the payload was a URL. They were transient errors, retrying the request was the recommended course of action and would typically result in a successful transcription.

  2. resolved

    The issue was resolved at 19:47 UTC.

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.

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: minor) posted by Deepgram, started 2026-06-17 13:35 UTC, resolved after 6.2 h, 2 update(s).

Title
400 errors with PreRecorded STT ("REMOTE_CONTENT_ERROR" / "failed to return valid data") when passing a URL
Vendor
Deepgram
Date
URL
https://rewindex.com/company/deepgram/incidents/28p5w85q9q6c

Deepgram profileRecent Deepgram incidentsAll outages on June 17, 2026Deepgram in June 2026MarkdownJSON