What 523 means
Unofficial, used by Cloudflare. Cloudflare can’t reach the website’s own server at all, usually because there’s no network route to its IP address.
When servers send it
When the origin’s IP address has changed, the DNS records are wrong, or there’s a routing problem between Cloudflare and the origin.
Common causes
- A wrong or out-of-date origin IP address in Cloudflare DNS.
- A routing problem at the hosting provider.
- In AWS, a VPC route table sending Cloudflare’s address range somewhere private.
How to fix it as a developer
- Check the A or AAAA records in Cloudflare match the server’s real IP address.
- Ask the host for a traceroute (MTR) from the origin to a Cloudflare IP address.
How to fix it as a visitor
- Try again later. The site can’t be reached right now.
Related codes
- 522 Connection Timed Out: Cloudflare couldn’t connect to the website’s server in time.
- 521 Web Server Is Down: The website’s server refused Cloudflare’s connection.
- 530 Origin DNS Error: Cloudflare couldn’t look up the website’s server. The page shows a 1xxx error with the details.
- 502 Bad Gateway: A proxy or load balancer got an invalid response, or none at all, from the server behind it.
Where it’s defined
523 isn’t in any RFC or the IANA status code registry. It’s used by Cloudflare. Reference: Cloudflare docs: error 523.
Other 5xx codes
500 Internal Server Error · 501 Not Implemented · 502 Bad Gateway · 503 Service Unavailable · 504 Gateway Timeout · 505 HTTP Version Not Supported · 511 Network Authentication Required · 520 Web Server Returned an Unknown Error · 521 Web Server Is Down · 522 Connection Timed Out · 524 A Timeout Occurred · 525 SSL Handshake Failed · 526 Invalid SSL Certificate
Or search them all in the HTTP status code list.