Skip to the content

522 Connection Timed Out

Cloudflare tried to connect to the origin server and got no reply in time. Often a firewall is dropping its packets.

Class
Unofficial codes. Not in the IANA registry. These are made up by one piece of software and mean nothing outside it, but they turn up in logs and on error pages often enough.
Used by
Cloudflare

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

When the connection to the origin is not established within Cloudflare's time limit, or goes quiet right after. The origin is overloaded or offline, a firewall silently drops Cloudflare's packets, or the DNS record at Cloudflare points to an address where the server no longer is.

What to do about it

As a visitor: try again later.

As the owner: check that the address in Cloudflare's DNS settings is the current one of the server, that the server is up and not overloaded, and that Cloudflare's IP ranges are let through the firewall without a rate limit. Cloudflare names blocked addresses as the most common cause.

Not to be confused with

521 Web Server Is DownThe origin refused the connection outright.
524 A Timeout OccurredThe connection worked, the response took too long.
504 Gateway TimeoutThe standard code for a gateway that waited too long.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12