DevToolsmith

Cloudflare 522 Connection Timed Out

Cloudflare 522 Connection Timed Out means the TCP connection to the origin server timed out. The server failed to fulfil a valid request. The problem is on the server side.

Class
5xx Server error
Standard
Non-standard (Cloudflare)
Cacheable by default
No
Safe to retry
Yes, usually

What Cloudflare 522 means

Cloudflare tried to connect to the origin and got no answer within the timeout. The origin is overloaded, offline, or a firewall silently drops Cloudflare’s packets instead of rejecting them.

522 isn’t defined in any HTTP standard. It is specific to Cloudflare, so other servers and proxies won’t use it.

How to fix error 522

  • Check the origin IP in Cloudflare DNS is correct and the server is reachable.
  • On Oracle Cloud, AWS and similar, open ports 80/443 in both the cloud firewall (security list or group) and the OS firewall.

Retrying

Yes, usually. It is often temporary, so retry with exponential backoff and give up after a few attempts.

Example response

HTTP/1.1 522 Connection Timed Out
Date: Wed, 21 Oct 2026 10:30:00 GMT
Server: cloudflare
CF-RAY: 8c2f6a1e3b9d4e21-FRA
Content-Type: text/html; charset=UTF-8

Related status codes

Other 5xx status codes

500 Internal Server Error · 501 Not Implemented · 502 Bad Gateway · 503 Service Unavailable · 504 Gateway Timeout · 505 HTTP Version Not Supported · 507 Insufficient Storage · 508 Loop Detected · 511 Network Authentication Required · 520 Web Server Returned an Unknown Error · 521 Web Server Is Down · 523 Origin Is Unreachable · 524 A Timeout Occurred · 525 SSL Handshake Failed · 526 Invalid SSL Certificate

See the full list of HTTP status codes.

Sources

Spotted a mistake? Email hello@devtoolsmith.com and we’ll fix it.

Frequently asked questions

What does Cloudflare 522 Connection Timed Out mean?

Cloudflare 522 Connection Timed Out means the TCP connection to the origin server timed out. Cloudflare tried to connect to the origin and got no answer within the timeout. The origin is overloaded, offline, or a firewall silently drops Cloudflare’s packets instead of rejecting them.

How do I fix Cloudflare 522?

Check the origin IP in Cloudflare DNS is correct and the server is reachable. On Oracle Cloud, AWS and similar, open ports 80/443 in both the cloud firewall (security list or group) and the OS firewall.