522 is a Cloudflare-specific code. It means Cloudflare timed out while contacting the origin web server: either the TCP handshake did not complete in time because the origin never answered Cloudflare's connection attempt, or the connection was established but the origin did not acknowledge Cloudflare's request.
Unlike with 521, where the origin refuses the connection, with 522 Cloudflare's packets go unanswered. That points to an overloaded origin, a firewall that silently drops Cloudflare's traffic, network problems between Cloudflare and the host, or a DNS record that points to an IP address where nothing responds.
Example response
HTTP/1.1 522 Connection Timed Out
Date: Fri, 06 Nov 2026 10:15:32 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
X-Frame-Options: SAMEORIGIN
Referrer-Policy: same-origin
Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: Thu, 01 Jan 1970 00:00:01 GMT
Server: cloudflare
CF-RAY: 8f3a1b2c4d5e6f72-LHRSEO and redirect checking
Like other origin errors, 522 makes the site unreachable for crawlers, and persistent errors lead to slower crawling and deindexing. Check that the origin IP address in Cloudflare's DNS settings is correct, that Cloudflare's IP ranges are allowed, and that the server is not overloaded.
Common causes and use cases
- The origin server is overloaded and cannot accept new connections.
- A firewall drops, rather than rejects, packets from Cloudflare's IP ranges.
- The DNS record points to a wrong or outdated IP address.
- Packet loss or routing problems between Cloudflare and the origin's network.