HTTP 523 Origin Is Unreachable

Non-standard, from Cloudflare: the origin could not be reached at all — typically a DNS record pointing at the wrong address or a routing problem.

Non-standard — not defined by any RFC. Vendor documentation: Cloudflare 5xx error reference

Where you meet HTTP 523 in production

After a DNS change points the hostname at an old or wrong address, when an origin's IP changes without the DNS record following, or when there is no route from the CDN to the origin's network.

Why you would test it

Usually a configuration error rather than load, so retrying rarely helps. A test can check that the client surfaces it as an outage, not as an invalid request.

What your client should do about a 523

Treat it as an outage that a retry will not fix quickly. Fail fast, surface a clear "service unavailable" state, and check DNS records first. Health checks should alert on it immediately rather than after several retries.

523 versus the codes it gets confused with

Endpoints that return 523

1 endpoint in this playground answers with 523. Every one is free, needs no signup, and can be called from the browser or with curl.

Questions about HTTP 523

What is the most common cause?
A DNS record that points at an address with nothing behind it, often after a migration.
Will it fix itself?
Rarely. It usually needs a configuration change.

Other server error codes

All HTTP status codes · All 55 mock REST APIs · Getting started guide

Last updated