| Previous | Next |
| HTTP_STATUS_AUTHENTICATION_REQUIRED | HTTP_STATUS_SERVER_IS_DOWN |
HTTP_STATUS_UNKNOWN_ERROR
Cloudflare reports 520 when it cannot classify the origin failure as a more specific HTTP error. Documented causes include origin crashes, firewalls blocking Cloudflare, oversized headers, malformed or empty responses, and broken HTTP/2 behavior at the origin.
Capture the Cloudflare Ray ID and response headers, then compare them with origin logs. Check origin response size, HTTP protocol implementation, and firewall policy before changing the client.
Operational meaning of HTTP 520 for HTTP_STATUS_UNKNOWN_ERROR
HTTP 520 (HTTP_STATUS_UNKNOWN_ERROR) is a server-error response. AllStat records its meaning as “520 Web Server Returned an Unknown Error”. For HTTP_STATUS_UNKNOWN_ERROR, interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling for HTTP_STATUS_UNKNOWN_ERROR
- Correlate HTTP_STATUS_UNKNOWN_ERROR with origin, gateway, load-balancer, and dependency logs to locate which hop generated it.
- For HTTP_STATUS_UNKNOWN_ERROR, record request and trace identifiers, upstream timing, retry count, and the health of the selected backend.
- For HTTP_STATUS_UNKNOWN_ERROR, use bounded retries with backoff only for idempotent work and only when the service policy permits them.
For telemetry, record HTTP 520, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.