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
HOW TO FIX IT
curl -v --resolve example.com:443:<origin-ip> https://example.com/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
Something went wrong on the server and it has nothing more specific to say. It's what most frameworks return when your code throws an exception it doesn't handle.
A server in the middle, like a load balancer, reverse proxy or CDN, tried to pass your request on to the server behind it and got back something it couldn't use. Either the upstream server didn't answer properly, or the connection closed before a full response came back.
The server is up but can't handle the request right now. It's meant to be temporary: overload, maintenance, or an app that isn't ready yet.
A proxy or load balancer forwarded your request and gave up waiting for the server behind it to answer.
Cloudflare-specific. Cloudflare tried to connect to your origin server and the connection was refused.
Cloudflare-specific. Cloudflare tried to connect to your origin and the connection timed out.
Cloudflare-specific. Cloudflare can't find a network route to your origin server.
Cloudflare-specific. Cloudflare connected to your origin but couldn't complete the TLS handshake with it.
Cloudflare-specific. Cloudflare couldn't find where to send the request: it couldn't resolve the origin's hostname, or the Cloudflare Tunnel for it isn't connected.
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.