Cloudflare Error 524: A timeout occurred while waiting for the origin
Also searched as: error 524 · 524 a timeout occurred
Is Cloudflare Error 524 happening on your domain?
An external probe reports actual response time, which tells you how close normal requests are running to the limit before they tip over.
Free, no signup. Runs from outside your network, which is the only way to tell a server fault from a local one.
Short answer
Cloudflare connected to the origin successfully, but the origin took longer than 100 seconds to send a complete response. The request is too slow, not unreachable.
What Cloudflare Error 524 means
524 is a response-time limit, not a connection failure. It fires on long-running requests: heavy reports, unbatched imports, slow third-party API calls inside the request path.
Causes and fixes, most likely first
A single request genuinely takes longer than 100 seconds.
Move the work to a background job and return immediately with a status the client can poll. Long synchronous requests are fragile regardless of the CDN.
A slow external API call blocks the response.
Set an aggressive timeout on outbound calls and degrade gracefully rather than blocking the whole response.
Database queries without indexes are slow under load.
Profile the slow endpoint and add the missing indexes. 524s that appear only at peak are usually query-plan problems.
Cloudflare Error 524 on specific platforms and devices
How to stop it happening again
- •Alert on response time approaching the CDN's limit, not just on the eventual failure.
- •Never put long-running work in a synchronous request path.
Frequently asked questions
Can I raise the 524 timeout?
Enterprise plans can extend it, but the durable fix is making the request finish faster or moving the work to a background job.