Cloudflare Error 524: A Timeout Occurred
Cloudflare connected to the origin, but the origin didn’t send an HTTP response within 100 seconds.
A timeout occurred Meaning
The request reached your app, but it took longer than Cloudflare’s proxy read timeout (100s on Free/Pro/Business). The work may still complete on the origin after the user sees the error.
Common causes
- Long-running request (reports, exports, imports)
- Slow database queries
- Origin overloaded and queueing
- Waiting on a slow external API
⚡ Quick fix
- Move long work to a background job and poll for status
- Optimize the slow query or endpoint
- Serve long-running endpoints from a grey-clouded (DNS-only) subdomain
- Enterprise plans can raise the timeout
Detailed fix by platform
Cloudflare
- Return quickly with 202 Accepted and a job ID; let the client poll a status endpoint.
How to diagnose
- Timing — How long does the endpoint take on origin?
- Bottleneck — DB, CPU or external call?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Cloudflare
Other ways to find it
Where this error sits
Origin: Edge & web server. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 12 Oct 2026