524 A Timeout Occurred

Cloudflare: the origin accepted the connection but did not send an HTTP response within 100 seconds.

524 at a glance

Code: 524
Name: A Timeout Occurred
Class: 5xx Server error
Status: Non-standard used by Cloudflare
Documented by: Cloudflare
Cacheable by default: No by default. Caches only store responses with unrecognised status codes if explicit freshness (Cache-Control max-age) is given.

What 524 means

Cloudflare returns 524 when it connected to the origin successfully but the origin took too long to send response headers. The default proxy read timeout is 100 seconds; Enterprise plans can raise it. The origin may still finish the work after Cloudflare gave up.

What typically causes a 524

Long-running requests: reports, exports, imports, heavy database queries.
Origin overloaded so requests queue for too long.
Backends waiting on slow third-party APIs.

Fix it on the server

Run long work in the background and return 202 with a polling URL, or stream progress.
Serve long-running endpoints from a hostname that is not proxied by Cloudflare (grey cloud) if they must stay synchronous.

Fix it as a client or visitor

Retry later or ask the site for an asynchronous export option.

Headers that go with 524

Header	Role
`CF-RAY`	Request ID for troubleshooting.

Example response

HTTP/1.1 524
Server: cloudflare
Content-Type: text/html