Skip to content

524 A Timeout Occurred

Cloudflare connected to the origin but the origin did not send a complete response within the time limit.

Status

HTTP/1.1 524 A Timeout Occurred

Details

  • Category: 5xx
  • Status: Unofficial (Cloudflare). Not registered with IANA. A server, framework, or CDN convention.
  • Specification: none, not defined by any RFC
  • Cacheable: Not cacheable
  • Response body: Allowed
  • Retry: Retry after a delay

524 is Cloudflare's version of a gateway timeout. The TCP connection succeeded and the request was delivered, but the origin did not finish responding within Cloudflare's proxy timeout, which is 100 seconds on standard plans.

It points at slow application work rather than at connectivity: long database queries, blocking third-party calls, or a request that is simply doing too much synchronously.

Common causes

  • A request taking longer than the edge proxy timeout to produce a response.
  • Long-running reports, exports, or migrations run through a web request.
  • A blocking call to a slow third-party service inside the request path.
  • Long-lived streaming connections that never complete a normal response.

How to fix it

As the client

  • Retry idempotent requests. Note the work may have completed at the origin even though you got no response.
  • Prefer an asynchronous endpoint if one exists.

As the server

  • Move long operations to a background job and return 202 with a status URL.
  • Profile the slow path. Raising timeouts hides the problem rather than fixing it.
  • Use a dedicated subdomain excluded from the proxy for genuinely long-lived connections.

Examples

A request that outran the edge timeout

HTTP request

GET /export/full-catalog HTTP/1.1
Host: www.example.com

HTTP response

HTTP/1.1 524
Server: cloudflare

See also