524 A Timeout Occurred — Causes & Fix
HTTP 524 (A Timeout Occurred) means Cloudflare made a connection to the origin but the origin didn't send a full response before Cloudflare's timeout (100s by default).
- Applies to
- Any website or web server (HTTP standard)
- Time to fix
- 15 minutes – 2 hours
What it means
Causes include a slow backend, a long-running request/query, or a process that hangs before responding. This is a Cloudflare-specific status code (not part of the HTTP standard). Cloudflare returns it when it sits in front of a site and has a problem reaching or getting a valid response from the origin (your) server — so the fix is almost always at the origin, not with the visitor.
Symptoms
- Cloudflare "Error 524" page
- Long requests fail after ~100 seconds
How to fix it
- 1
Speed up the response (operator)
1. Optimise the slow endpoint/query so it responds within the timeout. 2. Offload long jobs to background processing.
- 2
Adjust timeouts
1. On Enterprise plans, raise the Cloudflare proxy timeout; otherwise keep responses fast.
Frequently asked questions
Why does Error 524 happen on long requests?
Cloudflare cut the connection because the origin took too long to respond (default 100s). Make the endpoint respond faster or process long tasks in the background.
Last updated July 20, 2026
Guidance only — always consult a qualified professional or the official service manual before carrying out repairs.