Troubleshooting 5 min read

Proxy Error 503 Service Unavailable: Causes and Fixes in 2026

A 503 can come from the proxy, a CDN or the website itself, and each needs a different response. Here's how to tell them apart and what to change.

Proxy error 503 Service Unavailable means a server in the chain is temporarily unable to handle your request. Unlike a 407, which is about credentials, or a 404, which is about a missing page, a 503 is about capacity or availability right now. Through a proxy, that server can be the proxy gateway, the upstream it routes through, a CDN in front of the website, or the website itself. The fix depends on which one it is.

Where a 503 Through a Proxy Comes From

There are two main places a 503 can originate, and you can tell them apart with curl's verbose mode:

curl -v -x http://USERNAME:[email protected]:8080 https://example.com -o /dev/null 2>&1 | grep -E "^(<|>) (CONNECT|HTTP)"
  • "< HTTP/1.1 503" directly after "> CONNECT": the proxy accepted your credentials but couldn't establish the tunnel. On our gateway, a 503 or 502 on CONNECT usually means the target or an upstream failed, not that your login was rejected.
  • "< HTTP/1.1 200 Connection established" and later "< HTTP/2 503": the tunnel worked and the website answered with 503. That's the site telling you it's overloaded, in maintenance, or deliberately turning you away.

The distinction matters because a proxy-side 503 is fixed by retrying through a different exit, while a website-side 503 is fixed by slowing down, waiting, or changing how your traffic looks.

Website 503s: Overload, Maintenance and Soft Blocks

Websites return 503 for three broad reasons:

  1. Real overload or maintenance. The site is struggling for everyone. Check it from your own browser without a proxy. If it's down there too, wait.
  2. Rate limiting that uses 503 instead of 429. Some stacks answer too many requests with 503 rather than 429. If the 503s start after you ramp up concurrency and stop when you slow down, that's what's happening. Our 429 Too Many Requests guide covers rate limits in detail.
  3. Bot challenges. Some protection layers return a 503 status along with a JavaScript challenge page. If the response body contains a script-heavy interstitial rather than an error message, you're being challenged, not refused. A real browser solves it; a plain HTTP client can't. See Cloudflare access denied with proxies.

Read the Retry-After Header

A well-behaved server sending 503 often includes a Retry-After header, either as a number of seconds or an HTTP date. Respecting it is the fastest way to stop getting 503s, and it's polite to the site. Here's a minimal Python helper:

import time
import requests
from email.utils import parsedate_to_datetime
from datetime import datetime, timezone

PROXY = "http://USERNAME:[email protected]:8080"
proxies = {"http": PROXY, "https": PROXY}

def retry_after_seconds(value, default=10):
    if not value:
        return default
    if value.isdigit():
        return int(value)
    try:
        when = parsedate_to_datetime(value)
        return max(0, (when - datetime.now(timezone.utc)).total_seconds())
    except (TypeError, ValueError):
        return default

def fetch(url, attempts=4):
    for i in range(attempts):
        r = requests.get(url, proxies=proxies, timeout=30)
        if r.status_code != 503:
            return r
        wait = min(retry_after_seconds(r.headers.get("Retry-After")), 120)
        print(f"503, waiting {wait:.0f}s (attempt {i + 1})")
        time.sleep(wait)
    return r

print(fetch("https://example.com").status_code)

Capping the wait (120 seconds here) prevents a misconfigured header from stalling your job for hours.

Proxy-Side 503s: What to Check

  1. Retry with a new IP. With no session parameter, each request already gets a new IP. If you use a sticky session such as USERNAME-session-abc123-time-10, change the session id for the retry.
  2. Test a neutral target. If https://api.ipify.org works through the proxy but your target returns 503 on CONNECT, the target is unreachable from those exits. Try another country code, for example USERNAME-country-de.
  3. Check your plan. A plan out of bandwidth returns 402 on our gateway, and an inactive plan returns 407, so a 503 is not a billing message. Still, glance at the dashboard to rule it out.
  4. Reduce concurrency. Opening hundreds of tunnels to the same small site at once can trip its connection limits, which surfaces as gateway errors.

Why 503s Spike When You Scale Up

A common pattern: a scraper works fine at 5 concurrent requests and starts throwing 503s at 50. The proxy isn't getting worse; the target is reacting to volume. Rotating IPs spreads requests across many addresses, but many sites also rate limit by session cookie, by path, or globally per endpoint. More IPs don't help if the limit is on the endpoint itself.

  • Add jitter between requests instead of firing in fixed bursts.
  • Cache pages you've already fetched so retries don't refetch them.
  • Spread work across time. A job that runs overnight at a steady rate gets fewer 503s than one that runs in ten minutes.
  • Respect robots.txt and the site's terms. Our guide to proxy legality covers why that matters.

For a broader look at how sites decide to slow you down, read how to avoid blocks when web scraping.

Fixing 503 Errors with NodeProxies

Point your client at global.nodeproxies.xyz:8080 (HTTP) or global.nodeproxies.xyz:1080 (SOCKS5), leave the session parameter off so every retry gets a fresh residential IP, and add the Retry-After logic above. Billing is per GB with no subscription, and balance never expires, so you can pause a job when a target is struggling without paying for idle time. See the pricing page for per-GB rates.

FAQ

Is a 503 error caused by my proxy?

Only if it appears as the response to the CONNECT request. If the tunnel is established first and the 503 comes afterwards, the website sent it.

Will rotating IPs fix 503 errors?

They fix proxy-side 503s and per-IP rate limits. They don't fix a site that's down or one that limits by endpoint, and in those cases slowing down is the only real fix.

What is the difference between 502 and 503?

A 502 means a gateway got an invalid or no response from the next server. A 503 means a server is up but temporarily refusing to handle the request. See proxy error 502 Bad Gateway for the 502 side.

How long should I wait after a 503?

Use the Retry-After header if present. If not, start at a few seconds and double the wait on each retry, up to a cap of a minute or two.

NodeProxies

Ready to get started?

90M+ residential, mobile & datacenter proxies. Datacenter from $0.30/GB, residential from $0.42/GB. No contracts.

Create free account