524 A Timeout Occurred — What It Means and How to Fix It

What 524 means

Cloudflare established a TCP connection successfully and sent the request, but the origin did not return a complete response within its timeout — 100 seconds on most plans. Unlike a 522, the connection worked fine; the application is simply taking too long.

Common causes

•A long-running request such as a report, export, or bulk import.
•A slow database query blocking the response.
•A long-polling or streaming endpoint held open past the limit.
•A deadlock leaving the request hanging indefinitely.
•An external API call with no timeout of its own.

How to fix it

Move long-running work into a background job and return immediately with a job ID the client can poll. Cloudflare's timeout is not configurable on most plans, so restructuring the request is the fix rather than raising a limit. For genuine streaming, use WebSockets, which are not subject to the same timeout.

Catching 524 before your users report it

A 524 typically follows a period of rising response times. Alerting on response-time degradation gives you warning before requests start failing outright.

Monitor for 524 responses free

Often confused with

504 Gateway Timeout 522 Connection Timed Out

← All HTTP status codes

524 A Timeout Occurred — questions

Can I increase the Cloudflare 524 timeout?

Not on Free, Pro, or Business plans — the 100-second limit is fixed. Enterprise plans can adjust it. For everyone else the answer is to make the request finish faster or move the work to a background job.

Why do exports and reports cause 524 errors?

They do work synchronously inside the request. As data grows, the job crosses the 100-second line. Generate the file in a background job and let the user download it when it is ready.

524