Opens in a new tab

Cloudflare error 522: Connection timed out

Cloudflare tried to connect to your server and heard nothing back — no answer to the connection within 19 seconds, or no acknowledgement of the request within 90. Nothing refused it; the packets went unanswered. The usual reasons are a firewall silently dropping Cloudflare’s addresses, an old IP address in the DNS record, or a server too busy to answer.

Connection timed out
Error code 522
How 2 other clients word the same error

Browser tab

example.com | 522: Connection timed out

curl -I

HTTP/2 522
ErrorError 522: Connection timed out
Usually fixed byThe site owner or host
Status522 — Cloudflare’s own code
Connect timeout19 seconds, not adjustable
Request timeout90 seconds without an acknowledgement, once connected

Check the site from outside

Enter the address: we load it from our network and show the status code, how long it took, and the error if it failed.

What it means

Cloudflare sends a connection request (a SYN) and retries for 19 seconds. If the server never answers — or answers the connection but then does not acknowledge the request within 90 seconds — Cloudflare gives up and shows 522. A server that refuses the connection gives 521 instead; one that connects but is slow to answer gives 524.

Cloudflare’s own 522 page says the connection was made but the request did not finish; its documentation, updated in 2026, describes the two timeouts above.

Why it happens

  • A firewall dropping or rate limiting Cloudflare’s addresses — iptables, .htaccess rules, a security plugin — the most common cause, Cloudflare says.
  • The DNS record at Cloudflare still holds an old IP address, after a move to a new host or server.
  • An overloaded or offline server.
  • Keep-alive connections turned off on the server.
  • Packets dropped somewhere on the way to the server.

How to fix it

  1. Check that the A record in Cloudflare’s DNS holds the server’s current IP address — ask the host for it.
  2. Allow all of Cloudflare’s IP ranges (cloudflare.com/ips) in every firewall and security tool, without rate limits.
  3. Check the server’s load, and turn keep-alive on.
  4. For Cloudflare support, run an MTR or traceroute from the server to a Cloudflare IP address that used to connect.

If you are visiting the site

  • Nothing on your side causes it. Try again in a few minutes.

See it for yourself

curl -sv -o /dev/null --connect-timeout 20 https://example.com/ --resolve example.com:443:203.0.113.10
mtr -rwc 20 203.0.113.10

With the origin’s IP in place of 203.0.113.10. If curl times out from your computer too, the server or its network is not answering; if it answers you but not Cloudflare, a firewall is dropping Cloudflare.

Questions

What is the difference between 521, 522 and 524?

521: the server refused Cloudflare’s connection. 522: it never answered it. 524: it accepted the connection and the request, but did not send a response within 125 seconds.

Sources

Error text and meaning checked on 25 September 2026 against these official sources:

Know when your site goes down — before your visitors do

Add your site and we check it every few minutes, confirm a failure from another location — Europe, North America or Asia — before calling it down, and email you when it stops answering and when it is back. Free for two sites.

Create a free account