522: Connection Timed Out, what it means and what to do
This code is not part of the official HTTP standard. It comes from Cloudflare, the network that sits in front of a large share of the web, and you only see it on sites that use Cloudflare. Error 522 means Cloudflare could not complete the opening handshake with the origin server. Before any page is requested, two computers introduce themselves over TCP; a 522 means Cloudflare sent the introduction and heard nothing back in time. The origin may be offline, so overloaded it cannot answer, or a firewall may be silently discarding Cloudflare's packets, which produces the same silence. No request ever reached the website's software.
If you are just visiting a site
- Wait and retry in a few minutes. The problem sits between Cloudflare and the site's own server, and it often clears when that server recovers.
- There is nothing to fix on your device. A different browser, a cleared cache, or a restarted phone produces the same error, because your request reached Cloudflare successfully and failed after that.
- Tell the site owner through another channel if it persists, their social account or a status page. Owners often learn about origin failures from visitors first.
If it is your site behind Cloudflare
- Check whether the origin is up and reachable at all. If the server is down, rebooting or waiting out a host incident is the fix, and nothing in Cloudflare's panel changes it.
- Look for overload. A server at 100 percent CPU or with a saturated network link often stops answering new connections while still serving established ones. Resource graphs at the error timestamps tell the story.
- Whitelist Cloudflare's IP ranges at the origin firewall. Silent packet drops are the classic 522. Rate limiting rules and security appliances frequently single out Cloudflare's ranges because so many requests arrive from them.
- Check with the hosting provider for network issues. Routing problems and DDoS mitigation at the host can blackhole traffic before it reaches the machine.
Visitors: a 522 never got as far as the website itself. Owners: silence is the clue, something is dropping or ignoring the handshake, usually the firewall or an overwhelmed server.
Common questions
What is the difference between 522 and 524? A 522 fails at the very start: the connection to the origin could not be established. A 524 means the connection succeeded and the request was sent, but the origin took too long to produce an HTTP response. One never got in the door, the other got in and waited.
Why does a 522 come and go? Intermittent 522s usually mean the origin is near its limits, answering when load dips and going silent when it spikes, or that a firewall rate limit engages only at busy times. The pattern of when it fails is the diagnostic.
Related errors