← All status codes
520

Web Server Error

Cloudflare-specific. Cloudflare connected to your origin server and got a response it couldn't use, or no response at all.

It's Cloudflare's catch-all for origin responses that don't fit another 52x code. The request reached your server, so DNS and the connection are working. Look at what your server sent back.

What we see on Larm

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

11 monitors got a 520 in this period, but only 17 failed checks in total, so most cleared up within a check or two. The median time to first byte was 5,260 ms, much slower than other 5xx errors.

COMMON CAUSES

The origin server crashed or is misconfigured
A firewall or security plugin on the origin blocks Cloudflare's IPs
Response headers over 128 KB, often from too many cookies
An empty or malformed response with no status code
A wrong HTTP/2 configuration on the origin
Authenticated Origin Pulls is on, but the origin isn't set up to accept client certificates

HOW TO FIX IT

Check the origin's logs at the time of the error
Request the origin directly, bypassing Cloudflare, to see the raw response: curl -v --resolve example.com:443:<origin-ip> https://example.com/
Check the size of the response headers, including cookies
Turn off HTTP/2 to origin in Cloudflare to test whether that's the cause

What this means for monitoring

Monitoring the origin directly as well as the public URL helps narrow down a 520. If the origin check passes, look at the response headers and the connection between Cloudflare and the origin.

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.