524 is a Cloudflare-specific code. It means Cloudflare successfully connected to the origin web server, but the origin did not send an HTTP response before Cloudflare's proxy read timeout expired. Cloudflare currently documents a default of 125 seconds (older documentation says 100); Enterprise customers can raise it to as much as 6,000 seconds.
The connection itself works, so the problem is how long the application takes: long-running reports, large exports, slow database queries, or a backend waiting for another service. The origin may still finish the work after Cloudflare has given up; its logs then show a successful request, or a 499 in nginx.
Example response
HTTP/1.1 524 A Timeout Occurred
Date: Fri, 06 Nov 2026 10:15:32 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
X-Frame-Options: SAMEORIGIN
Referrer-Policy: same-origin
Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: Thu, 01 Jan 1970 00:00:01 GMT
Server: cloudflare
CF-RAY: 8f3a1b2c4d5e6f74-NRTSEO and redirect checking
A 524 is a server error for crawlers. Pages that take more than a few seconds are already a crawling problem, long before they reach Cloudflare's limit. Move slow work to background jobs, return 202 with a status URL, or stream the response. The Redirect Latency Checker shows how long each hop takes.
Common causes and use cases
- A long-running script, report or export takes longer than Cloudflare's timeout of about two minutes.
- Slow database queries or locked tables.
- The application waits for a slow external API.
- Exhausted resources on the origin (CPU, memory, worker pool) make every request slow.