# 400 errors with PreRecorded STT ("REMOTE\_CONTENT\_ERROR" / "failed to return valid data") when passing a URL

- Provider: [Deepgram](https://down.guide/providers/deepgram)
- Confidence: Confirmed
- Impact: Degraded
- lasted 6h 13m
- started 2026-06-17 13:35 UTC
- Batch API
- id: DWN-32b9db8534
- Official page: https://stspg.io/m1j68sqyrg25

## Updates from Deepgram
### 2026-06-17 13:35 UTC: 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.

### 2026-06-17 19:47 UTC: resolved
The issue was resolved at 19:47 UTC.

From the builder: does your app depend on Deepgram? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=deepgram) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Deepgram.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-32b9db8534), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
