Cloudflare 521: cause and troubleshooting
The origin web server refused Cloudflare's TCP connection, often because the service is down or a firewall blocks Cloudflare addresses.
What to check next
Confirm the origin is listening on the configured port, inspect firewall and security-group rules, and allow the published Cloudflare egress ranges where appropriate.
Use the diagnostic code and provider headers as clues, then confirm the request against origin logs and deployment telemetry. A status code can be generated by a proxy, load balancer, function platform, or origin application; the same number does not always have the same cause across providers.
Keep a CDN error from becoming a long outage
Record the request identifier, timestamp, affected hostname, and deployment when investigating an intermittent failure. SteadyNode checks public endpoints on a schedule and translates recognized upstream errors into concise diagnostic context, helping teams identify whether a failure is at the edge or origin.

