--- title: "HTTP 522 Connection Timed Out — Meaning & Fix" description: "HTTP 522 Connection Timed Out explained: what it means, common causes, how to fix it and how to monitor for it." url: https://uptrack.app/http/522 ---

# HTTP 522 Connection Timed Out

A Cloudflare-specific status code meaning Cloudflare could not establish a TCP connection to the origin server within 15 seconds. The origin server is unreachable — it is either down, firewalled, or overloaded. ## What does HTTP 522 mean? A Cloudflare-specific status code meaning Cloudflare could not establish a TCP connection to the origin server within 15 seconds. The origin server is unreachable — it is either down, firewalled, or overloaded. ## Common causes 1. 1 The origin server is down or not listening on the expected port. The server process has crashed or was never started. 2. 2 A firewall, security group, or iptables rule is blocking Cloudflare's IP ranges from reaching the origin server. 3. 3 The origin server is overloaded and its TCP connection backlog is full, causing new connections to be dropped. ## How to fix it 1. 1 Verify the origin server is running and listening on the correct port. Check with ss -tlnp or netstat to confirm. 2. 2 Whitelist all Cloudflare IP ranges in your firewall. Cloudflare publishes its IP list at cloudflare.com/ips. If you restrict access to Cloudflare IPs only, ensure the list is up to date. 3. 3 If the server is overloaded, scale resources or reduce traffic. Check for connection limits in your server config (e.g., worker\_connections in nginx). ## Monitor for HTTP 522 errors A 522 means your server is completely unreachable from Cloudflare — this is a full outage for all users behind the CDN. Uptrack detects it within 30 seconds and alerts you once several locations confirm it, so you can restore connectivity fast. ## Catch HTTP errors before your users do Start free, or choose a plan, for 30-second monitoring and alert confirmation. [See plans](https://uptrack.app/pricing) from $3/mo · 30-day money-back guarantee ## Other HTTP status codes - [HTTP 520 Web Server Returns Unknown Error](https://uptrack.app/http/520) - [HTTP 504 Gateway Timeout](https://uptrack.app/http/504) - [HTTP 503 Service Unavailable](https://uptrack.app/http/503) - [HTTP 502 Bad Gateway](https://uptrack.app/http/502) - [HTTP 500 Internal Server Error](https://uptrack.app/http/500) - [HTTP 451 Unavailable For Legal Reasons](https://uptrack.app/http/451) - [HTTP 429 Too Many Requests](https://uptrack.app/http/429) - [HTTP 422 Unprocessable Entity](https://uptrack.app/http/422) - [HTTP 415 Unsupported Media Type](https://uptrack.app/http/415) - [HTTP 413 Payload Too Large](https://uptrack.app/http/413) - [HTTP 410 Gone](https://uptrack.app/http/410) - [HTTP 409 Conflict](https://uptrack.app/http/409) - [HTTP 408 Request Timeout](https://uptrack.app/http/408) - [HTTP 405 Method Not Allowed](https://uptrack.app/http/405) - [HTTP 404 Not Found](https://uptrack.app/http/404) - [HTTP 403 Forbidden](https://uptrack.app/http/403) - [HTTP 401 Unauthorized](https://uptrack.app/http/401) - [HTTP 400 Bad Request](https://uptrack.app/http/400) - [HTTP 304 Not Modified](https://uptrack.app/http/304) - [HTTP 302 Found](https://uptrack.app/http/302) - [HTTP 301 Moved Permanently](https://uptrack.app/http/301) - [HTTP 204 No Content](https://uptrack.app/http/204) - [HTTP 201 Created](https://uptrack.app/http/201) - [HTTP 200 OK](https://uptrack.app/http/200)