Cloudflare 524 A Timeout Occurred: Causes and Fixes

What Cloudflare 524 means

Cloudflare connected and sent the request, but the origin didn’t return an HTTP response within 100 seconds (the default on most plans). It is Cloudflare’s version of 504, usually caused by long-running requests like exports or reports.

524 isn’t defined in any HTTP standard. It is specific to Cloudflare, so other servers and proxies won’t use it.

How to fix error 524

Move long work to a background job and poll for the result, or stream progress to keep the connection busy.
For long-running admin endpoints, use a hostname that isn’t proxied through Cloudflare.

Retrying

Yes, usually. It is often temporary, so retry with exponential backoff and give up after a few attempts.

Example response

HTTP/1.1 524 A Timeout Occurred
Date: Wed, 21 Oct 2026 10:30:00 GMT
Server: cloudflare
CF-RAY: 8c2f6a1e3b9d4e21-FRA
Content-Type: text/html; charset=UTF-8

Related status codes

504 Gateway Timeout : A proxy or gateway didn’t get a response from the upstream server in time.
522 Connection Timed Out : The TCP connection to the origin server timed out.
202 Accepted : The request was accepted for processing, but the work isn’t finished yet.

Other 5xx status codes

500 Internal Server Error · 501 Not Implemented · 502 Bad Gateway · 503 Service Unavailable · 504 Gateway Timeout · 505 HTTP Version Not Supported · 507 Insufficient Storage · 508 Loop Detected · 511 Network Authentication Required · 520 Web Server Returned an Unknown Error · 521 Web Server Is Down · 522 Connection Timed Out · 523 Origin Is Unreachable · 525 SSL Handshake Failed · 526 Invalid SSL Certificate

See the full list of HTTP status codes.

Sources

Cloudflare docs: 5xx errors

Spotted a mistake? Email hello@devtoolsmith.com and we’ll fix it.

Frequently asked questions

What does Cloudflare 524 A Timeout Occurred mean?

Cloudflare 524 A Timeout Occurred means the origin accepted the connection but didn’t respond within 100 seconds. Cloudflare connected and sent the request, but the origin didn’t return an HTTP response within 100 seconds (the default on most plans). It is Cloudflare’s version of 504, usually caused by long-running requests like exports or reports.

How do I fix Cloudflare 524?

Move long work to a background job and poll for the result, or stream progress to keep the connection busy. For long-running admin endpoints, use a hostname that isn’t proxied through Cloudflare.