Cloudflare, after waiting 100 seconds for the origin.
Cloudflare error 524 — A timeout occurred
Cloudflare connected to the origin successfully and then waited out its 100-second limit without a complete response. The request very likely IS being processed — it is just slow.
A proxy does not fix this. The 100-second budget is Cloudflare's, and it starts after your request has already arrived. Where you connected from does not enter into it.
Why it happens
An expensive endpoint: a report, a search across a large dataset, an export.
The origin is thrashing under load.
A long-polling or streaming endpoint that Cloudflare's proxy timeout is not suited to.
How to fix it
- Ask for less per request — narrow the query, page the results.
- If it is your own site, move the work to a job and return a ticket.
- Retry, and expect the same result until the underlying work gets faster.
FAQ
What does 524 mean?›
Cloudflare connected to the origin successfully and then waited out its 100-second limit without a complete response. The request very likely IS being processed — it is just slow. Cloudflare, after waiting 100 seconds for the origin.
Why am I getting 524?›
An expensive endpoint: a report, a search across a large dataset, an export. The origin is thrashing under load. A long-polling or streaming endpoint that Cloudflare's proxy timeout is not suited to.
How do I fix 524?›
Ask for less per request — narrow the query, page the results. If it is your own site, move the work to a job and return a ticket. Retry, and expect the same result until the underlying work gets faster.
Will a proxy fix 524?›
The 100-second budget is Cloudflare's, and it starts after your request has already arrived. Where you connected from does not enter into it.