SteadyNode

Fastly · HTTP 503

Fastly 503: Backend Fetch Failed

Investigate Fastly backend fetch failed responses by checking backend health, DNS, TLS, origin timeouts, and VCL request routing.

Origin / Network Firewall

Decode a CDN or gateway error

Paste a captured HTTP response or enter a status and headers. Only the status and response headers are sent; common credential headers are filtered first.

Supports raw headers, full HTTP responses, JSON with status/statusCode and headers, cURL -v/-i response output, and HAR exports. HAR selects a server error first. cURL commands are never executed; request headers, response bodies, and common credential headers are excluded.

Diagnostic report

Error code / name

FASTLY-BACKEND_FETCH_FAILED

Fault domain

Origin / Network Firewall

Why it happened

Fastly could not fetch a response from the selected backend. DNS failure, a refused or timed-out connection, TLS verification, or an origin response error can all surface as backend fetch failed.

Actionable fixes

  1. Use the Fastly request ID and backend logs to identify the selected origin and fetch error.
  2. Check backend hostname resolution, TLS certificate validation, connect timeout, and response timeout.
  3. Confirm the VCL host and port match the origin and that the origin accepts traffic from Fastly.

Why this error happened

Fastly could not fetch a response from the selected backend. DNS failure, a refused or timed-out connection, TLS verification, or an origin response error can all surface as backend fetch failed.

Actionable fixes

  1. Use the Fastly request ID and backend logs to identify the selected origin and fetch error.
  2. Check backend hostname resolution, TLS certificate validation, connect timeout, and response timeout.
  3. Confirm the VCL host and port match the origin and that the origin accepts traffic from Fastly.

Network failure point

Client -> Fastly POP -> VCL selects backend -> origin fetch fails -> X 503

Verify origin directly via CLI

curl -sS -v -I --connect-timeout 5 --max-time 20 --resolve www.example.com:443:ORIGIN_IP https://www.example.com/health

Configuration fix

main.vclvcl
backend origin {
  .host = "origin.example.com";
  .port = "443";
  .use_ssl = true;
  .ssl_check_cert = true;
  .connect_timeout = 2s;
}

Catch this failure before it becomes an outage

SteadyNode's Upstream Translator recognizes gateway signatures such as backend fetch failed and combines them with regional response timing to focus origin investigation.

No credit card required.

Start for free

Frequently asked questions

What does Fastly backend fetch failed mean?

Fastly selected a backend but could not obtain a usable response from it.

Can an origin certificate cause Fastly 503?

Yes. Backend TLS verification can fail when the hostname, certificate chain, or trust configuration is incorrect.

More CDN and gateway error guides

Cloudflare

Vercel and Netlify

AWS CloudFront and ALB

Fastly

Heroku and Render

Nginx and Envoy