Fastly 503 Backend Read Error / Connection Timeout
Quick answer
A Fastly 503 on a backend error usually means Fastly could not connect to or get a timely response from your origin. Check origin reachability, then raise the origin timeouts.
Most likely fix: Raise origin timeouts
How to fix it
Try these in order — the most common fix is first.
1. Raise origin timeouts
- Open the service in the control panel and click Clone to edit
- Click Origins and click the host name
- Click Advanced options and enter larger values under Timeouts
- Click Update, then activate on Production
Did this fix it?2. Check that Fastly can reach the origin
- Confirm the origin host resolves (a Gethostbyname error means NXDOMAIN)
- Allowlist Fastly public IP addresses in your firewall or network ACL
- Confirm the origin answers requests quickly from outside your network
Did this fix it?3. Add health checks and a failover origin
- Set up a health check on the primary origin
- Enable automatic load balancing on the primary and failover hosts
- Attach a condition to the failover host: backend.F_Primary.healthy == false (use backend.autodirector_.healthy == false for several primaries)
- Activate on Production
Did this fix it?
Symptoms
Visitors get a 503 Service Unavailable from Fastly with a backend read error or connection timeout.
Why it happens
- Origin server is slow, down or overloaded
- Firewall or ACL blocks Fastly IP addresses (connection refused)
- Origin hostname does not resolve (NXDOMAIN)
- Connection timeout in the origin settings is too low for a slow origin
- No failover origin and no health check configured
This guide also covers
- fastly 503 backend unavailable
- fastly error 503 first byte timeout
- fastly 503 service unavailable
- fastly connection timeout
Still not working?
If Fastly keeps failing, you're not alone. See every Fastly problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
All not loading, error messages & connection guides →
Cloudflare Error 521: Web Server Is Down (Cloudflare)
Other Fastly errors
- Fastly Error: Unknown Domain
- Fastly Purge Not Working (Old Content Still Served)
- Fastly TLS Certificate Stuck Pending or Not Provisioning
- Fastly Origin TLS Errors: Hostname Mismatch, Unable to Verify Certificate
- Fastly Not Caching: Always X-Cache MISS
- Fastly Serves Wrong Content or Denies Requests From Origin (Override Host)
- How to Cancel Fastly Account