Cloudflare error · 523
Cloudflare error 523: origin is unreachable
Cloudflare error 523 means the edge could not reach your origin at all. The network path failed before a normal connection refusal or HTTP response. “Origin is unreachable” is Cloudflare’s name for that failure.
HTTP status codes explained · the longer reference on the blog.
What 523 means
523 is Cloudflare’s code. The origin did not choose it. Cloudflare tried to contact the origin and the attempt failed because the address could not be reached: a DNS failure looking up the origin, an unroutable network, or a host that the edge’s network cannot get to. Visitors still see a Cloudflare error page, because the visitor reached Cloudflare.
Compare the neighbors. 521 means the IP was reached and refused. 522 means the connection attempt hung. 523 means Cloudflare could not get to the origin in the first place. A wrong origin hostname inside a Cloudflare spectrum or a CNAMEd origin that no longer resolves is a typical 523. An origin that is simply stopped is more often 521.
Common causes
The origin hostname does not resolve
Cloudflare is configured with a hostname for the origin, and that name no longer has a DNS record. The edge cannot pick an IP, so the origin is unreachable.
The IP is unroutable from Cloudflare
The record points at a private address, an address that was withdrawn, or a network that does not announce a route. Packets have nowhere to go.
The origin network is down
The provider’s router, the instance’s network interface, or the whole subnet is offline. The machine is not refusing connections. It is absent.
A recent DNS or IP change left a stale target
The public site moved, and Cloudflare still has the previous origin. Until the origin setting is updated, the edge keeps trying the unreachable target.
How to fix it
Resolve the origin the same way Cloudflare does
Look at the DNS record or the origin hostname in the Cloudflare dashboard. Query that name. If it does not resolve to the server you intend, fix the record.
Make sure the address is a public origin
Cloudflare cannot connect to a private LAN address. Use the public IP of the server that should answer, and confirm that IP is assigned to a live instance.
Check with the host if the route is gone
If the IP is correct and still unreachable from outside, the provider’s network is the outage. The web server config will not change what the edge can route to.
Retry the public URL after the record is corrected
Give the updated origin a moment, then request the hostname again. A 200 through Cloudflare means the edge can reach the new origin.
Is it your site, or just you?
Everyone who uses the proxied hostname shares this error. Confirm on a second network. Your browser cache is not a likely cause, because the page is generated at the edge.
The homepage checker follows the public name. Error 523 from the checker means our request also stopped at Cloudflare. Fix the origin address, then run the checker again to see the new status.
How to monitor for 523
A monitor on the public URL expects 200 and fails on 523. The alert includes the status, so you can tell an unreachable origin from an application 500. After the origin is reachable and returns 200, the next check sends a recovery alert. Free monitors check every 10 minutes.
The checker on the ismysiteup homepage requests the URL from our servers and shows the HTTP status, response time, and SSL details. No account is required, and that checker allows 5 checks per hour from the same network. A free account watches 5 URLs, each checked every 10 minutes, and sends alerts on WhatsApp, Telegram, Slack, or email. A monitor expects HTTP 200 unless you set a different expected status (100–599). One failed check is confirmed with a second check before the first alert, and a later success sends a recovery alert. Pro (every 5 minutes) and Business (every minute) are listed on the pricing page; paid checkout is not open yet.
Related status codes
- 521Web Server Is DownCloudflare reached the origin IP, and the origin refused the connection.
- 522Connection Timed OutCloudflare tried to open TCP to the origin and the handshake never finished.
- 520Web Server Returned an Unknown ErrorCloudflare connected, and the origin’s reply was empty or not valid HTTP.
FAQ
What does Cloudflare error 523 mean?
Cloudflare could not reach the origin. The failure is the path or the address, so the origin never handled the HTTP request.
How is 523 different from 521?
521 means Cloudflare reached the IP and the port refused the connection. 523 means Cloudflare could not reach the origin. A stopped web server on a live machine is usually 521.
Can I monitor a 523 without Cloudflare access?
Yes. The public URL returns 523 to any client that goes through the proxy, including a monitor. You still need the origin and DNS fixed on the server side. The monitor tells you when the public URL recovers.