SteadyNode

Cloudflare HTTP 522

What does Cloudflare error 522 mean?

Decode Cloudflare 522 connection timeouts, distinguish an unreachable origin from a slow response, and see what to check first.

Decode a CDN or gateway error

Paste a captured HTTP response or enter a status and headers. Only the status and response headers are sent; common credential headers are filtered first.

Supports raw headers, full HTTP responses, JSON with status/statusCode and headers, cURL -v/-i response output, and HAR exports. HAR selects a server error first. cURL commands are never executed; request headers, response bodies, and common credential headers are excluded.

Find the cause of the next outage sooner

During an outage, every second counts. SteadyNode's uptime engine translates CDN errors into likely root causes on every check.

No credit card required.

Start for free

Cloudflare 522: cause and troubleshooting

Cloudflare timed out while establishing a connection to your origin server.

What to check next

Check origin availability and network routes, review firewall allowlists and connection limits, and compare the reported Ray ID with origin-side logs.

Use the diagnostic code and provider headers as clues, then confirm the request against origin logs and deployment telemetry. A status code can be generated by a proxy, load balancer, function platform, or origin application; the same number does not always have the same cause across providers.

Keep a CDN error from becoming a long outage

Record the request identifier, timestamp, affected hostname, and deployment when investigating an intermittent failure. SteadyNode checks public endpoints on a schedule and translates recognized upstream errors into concise diagnostic context, helping teams identify whether a failure is at the edge or origin.

Frequently asked questions

What does a Cloudflare 522 mean?

Cloudflare could not establish a connection to the origin within the allowed time.

Is a 522 the same as a 524?

No. A 522 is a connection timeout; a 524 generally means the connection succeeded but the origin did not return an HTTP response in time.