HTTP 522 in Cloudflare

TCP handshake with the origin timed out (>15s).

Why Cloudflare returns 522

TCP handshake with the origin timed out (>15s).

How to fix it

Check origin CPU/network saturation and firewall rules; raise the origin's keep-alive.

Where this surfaces in Cloudflare

The Cloudflare edge before your origin ever sees the request. Look at the Ray ID in the response.

Cloudflare — CDN, WAF, and edge network in front of your origin.

What HTTP 522 means generally

Cloudflare could not negotiate a TCP handshake with the origin server.

HTTP 522 is a Cloudflare-specific error indicating that the TCP connection to the origin server timed out. Cloudflare tried to connect but the origin didn't respond within 15 seconds.

Other common causes of 522

• Origin server is overloaded
• Network issues between Cloudflare and origin
• Firewall rate-limiting Cloudflare requests
• Origin server has keepalive disabled

SEO impact

Site appears down to all visitors and crawlers. Extended 522s will hurt rankings.

How to catch it next time

LemWatch detects Cloudflare-specific errors and provides targeted troubleshooting advice for CDN-related issues.