Error 523: Origin is unreachable
Cloudflare has no route to your origin
Seen in Cloudflare
Cloudflare cannot reach the origin's IP address at all, usually because of a wrong DNS record or a routing problem.
Common causes
- The A or AAAA record in Cloudflare points to the wrong, old or private (RFC 1918) IP address.
- A routing problem between Cloudflare and the origin network.
- The hosting provider changed the server's IP address.
How to fix it
- Confirm the origin IP in the Cloudflare DNS records matches the server's current public IP.
- Check whether the IP is public and routed.
- If the record is right, ask the host for an MTR or traceroute from the origin to a Cloudflare IP.
Got a different message? Paste it into the error explainer.
Related errors
- 502 Bad Gateway · The proxy got a bad response from the server behind it
- 503 Service Unavailable · The server is temporarily unable to handle requests
- 504 Gateway Timeout · The server behind the proxy took too long
- Error 520: Web server is returning an unknown error · Cloudflare got an empty or invalid response
- Error 521: Web server is down · Cloudflare could not connect to your origin
- Error 522: Connection timed out · Cloudflare timed out connecting to your origin
- Error 525: SSL handshake failed · Cloudflare could not complete TLS with your origin
- Error 526: Invalid SSL certificate · Cloudflare doesn't trust your origin's certificate
- 429 Too Many Requests · You've hit a rate limit
- 400 Bad Request · The server could not understand the request
- 401 Unauthorized · The request needs valid credentials
- 403 Forbidden · The server refuses to allow this request