proxy_unavailable (5004, HTTP 503) · TranscriptFetch API error

The upstream egress proxy refused the tunnel (billing, credentials, or exhausted quota). NOT retryable - retrying cannot clear it, and every platform is affected until it is resolved.

Number5004

HTTP status503Service Unavailable

Familytransient5xxx · transient, retry with backoff

Example response

JSON

{
  "ok": false,
  "request_id": "req_…",
  "error": {
    "code": "proxy_unavailable",
    "number": 5004,
    "message": "The upstream egress proxy refused the tunnel (billing, credentials, or exhausted quota). NOT retryable - retrying cannot clear it, and every platform is affected until it is resolved.",
    "docs": "https://transcriptfetch.com/docs/errors/proxy_unavailable"
  }
}

Every failure carries error.code, error.number, error.message and error.docs, plus at most one of retry_with (the request change that would succeed), details (structured specifics) or issues (validation problems).

What it means

Egress proxy unavailable. The upstream egress proxy refused the tunnel (billing, credentials, or exhausted quota). NOT retryable - retrying cannot clear it, and every platform is affected until it is resolved.

Shown to end users as: “Fetching is temporarily unavailable. This is on our side and we are already aware of it.”

Why it happens

Egress proxy unavailable. The upstream egress proxy refused the tunnel (billing, credentials, or exhausted quota). NOT retryable - retrying cannot clear it, and every platform is affected until it is resolved.
Transient by definition: the same request may succeed a moment later.

What to do

This is an incident on our side, not a problem with your request. Retrying seconds later cannot clear it; every platform is affected until it is resolved.
Retry once the incident is resolved. Failed requests are never charged.

Retryable? Not usefully. Retrying cannot clear it; wait until the incident on our side is resolved, then retry. Every error response carries a request_id; include it when contacting support.