← All status codes
522

Connection Timed Out

Cloudflare-specific. Cloudflare tried to connect to your origin and the connection timed out.

Cloudflare waits 19 seconds for the origin to answer the TCP handshake, and once connected, 90 seconds for the origin to acknowledge the request. If either runs out, you get a 522. Unlike 521, nothing refused the connection. The packets went unanswered.

What we see on Larm

Failed HTTP checks on Larm from 9 October to 8 November 2026, across about 130 monitors.

No monitor on Larm got a 522 in this period. Larm's default check timeout is 10 seconds, so a check against an unreachable origin times out before Cloudflare gives up at 19.

COMMON CAUSES

A firewall or rate limiting silently drops Cloudflare's traffic. Cloudflare lists this as the most common cause
The origin server is overloaded or offline
The origin IP in Cloudflare DNS doesn't match the server's current IP
Keep-alive is turned off on the origin

HOW TO FIX IT

Allow all of Cloudflare's IP ranges, and check tools like fail2ban that block IPs automatically
Check that the A or AAAA record in Cloudflare matches the server's current IP
Check the origin's load
Turn on keep-alive on the origin web server

What this means for monitoring

Because Cloudflare waits 19 seconds before sending a 522, a monitor with a shorter timeout records a timeout before the 522 arrives.

Related status codes

5xx Server Error

Get alerted when your endpoints return unexpected status codes.

Larm checks your HTTP endpoints from multiple global locations and alerts you when they return status codes outside your expected range.