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
The origin server is down or not listening on the expected port. The server process has crashed or was never started.
- 2
A firewall, security group, or iptables rule is blocking Cloudflare's IP ranges from reaching the origin server.
- 3
The origin server is overloaded and its TCP connection backlog is full, causing new connections to be dropped.
How to fix it
- 1
Verify the origin server is running and listening on the correct port. Check with ss -tlnp or netstat to confirm.
- 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
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.
from $3/mo · 30-day money-back guarantee
Other HTTP status codes
- HTTP 520 Web Server Returns Unknown Error
- HTTP 504 Gateway Timeout
- HTTP 503 Service Unavailable
- HTTP 502 Bad Gateway
- HTTP 500 Internal Server Error
- HTTP 451 Unavailable For Legal Reasons
- HTTP 429 Too Many Requests
- HTTP 422 Unprocessable Entity
- HTTP 415 Unsupported Media Type
- HTTP 413 Payload Too Large
- HTTP 410 Gone
- HTTP 409 Conflict
- HTTP 408 Request Timeout
- HTTP 405 Method Not Allowed
- HTTP 404 Not Found
- HTTP 403 Forbidden
- HTTP 401 Unauthorized
- HTTP 400 Bad Request
- HTTP 304 Not Modified
- HTTP 302 Found
- HTTP 301 Moved Permanently
- HTTP 204 No Content
- HTTP 201 Created
- HTTP 200 OK