← All status codes
521

Web Server Down

Cloudflare-specific. Cloudflare tried to connect to your origin server and the connection was refused.

Refused means something answered and said no: nothing is listening on the port, or a firewall rejected the connection. If the connection attempt hangs instead, you get a 522.

What we see on Larm

Failed HTTP checks on Larm from 9 October to 8 November 2026, across about 130 monitors.

7 monitors got a 521 in this period, 11 failed checks in total.

COMMON CAUSES

The web server process stopped or crashed
A firewall or security software blocks Cloudflare's IPs
The origin isn't listening on port 443 with SSL mode Full or Full (strict), or on port 80 with Flexible
The origin server is restarting

HOW TO FIX IT

Check that the web server is running and listening on the right port, for example with ss -tlnp
Allow all of Cloudflare's IP ranges, listed at cloudflare.com/ips, in your firewall
Make sure the port the origin listens on matches your Cloudflare SSL mode
Check the origin's logs for a crash

What this means for monitoring

With 521, visitors get a Cloudflare error page instead of your site, so any monitor on the public URL will catch it. A separate monitor on the origin tells you whether the server itself is down or only unreachable from Cloudflare.

Related status codes

5xx Server Error

Get alerted when your endpoints return unexpected status codes.

Larm checks your HTTP endpoints from multiple global locations and alerts you when they return status codes outside your expected range.