522 Connection Timed Out
unofficial · Cloudflare
Cloudflare's TCP connection to the origin server timed out.
522 means Cloudflare tried to open a TCP connection to the origin and got no answer before its connection timeout. Packets went missing somewhere: a firewall silently dropping Cloudflare's traffic, a DNS record pointing at the wrong IP, or a server too overloaded to accept new connections.
| Class | Unofficial (Cloudflare) |
|---|---|
| Retry? | With backoff (idempotent requests only) |
| Cacheable by default | No — only with explicit Cache-Control |
| Response body | Allowed |
| Defined in | Cloudflare docs — Troubleshooting Cloudflare 5XX errors |
Example response
HTTP/1.1 522 Connection Timed Out
Content-Type: application/json
Content-Length: 32
{"error":"Connection Timed Out"}Common causes
- An origin firewall dropping (not rejecting) Cloudflare's IP ranges.
- The Cloudflare DNS record points at an old or wrong origin IP.
- The origin is overloaded or out of connection slots.
- Network or routing problems at the hosting provider.
How to fix it
- Confirm the A/AAAA record in Cloudflare points at the current origin IP.
- Allow Cloudflare's IP ranges, and check rate limiters aren't blocking them.
- Check origin load and connection limits.
- If the server is up but unreachable, contact the host.
Check what a URL returns
Print just the status line from the command line, or check a whole list of URLs at once, with their response headers, in the HTTP Status Checker.
curl -sI https://example.com/your-path | head -n 1
Frequently asked questions
My server is up — why do I get 522?
Cloudflare can't reach it. Most often a firewall drops Cloudflare's traffic, or the DNS record still points at an old IP.
Related status codes