HTTP 522 — Connection Timed Out

What 522 actually means

Another Cloudflare code rather than a real HTTP one. Where 521 is an active refusal, 522 is silence: Cloudflare sent a connection request to the origin and the TCP handshake never completed before the timeout. That pattern — packets going out and nothing coming back — points at a firewall dropping rather than rejecting traffic, a wrong IP address in DNS, or an origin so overloaded it cannot accept new connections.

Common causes

• A firewall silently dropping packets from Cloudflare instead of rejecting them
• The origin IP in Cloudflare's DNS pointing at the wrong or an old server
• The origin server overloaded and unable to accept new connections
• Network routing problems between Cloudflare and the origin
• The origin server's connection backlog full
• Keep-alives disabled at the origin, exhausting the port range under load

If you're just trying to view the page

1. Reload after a minute or two; overload-related 522s often clear
2. Nothing else — the failure is between Cloudflare and the site's server
3. Report it with the Ray ID if it persists

If it's your site

1. Check the origin firewall for DROP rules affecting Cloudflare IP ranges — dropping is what turns a 521 into a 522
2. Verify the A/AAAA record in Cloudflare points at the correct current origin IP
3. Look at server load, connection counts and the accept backlog on the origin
4. Enable keep-alives at the origin; Cloudflare relies on them and disabling them causes intermittent 522s
5. Test the origin directly from outside your network on the same port to confirm reachability

Reference

Status code

522

Reason phrase

Connection Timed Out

Category

5xx — Server Error

Cacheable by default

No