5xx Server error · unofficial (Cloudflare)

524 A Timeout Occurred

Cloudflare connected to the origin, but it didn't respond within 100 seconds.

What 524 means

The origin accepted the connection but took too long to send a response, usually because of a slow script or query.

Common causes

A long-running request (reports, exports, big queries) over Cloudflare's 100-second limit.

How to fix it

If you're calling an API

Retry; for slow operations, use the API's async or export endpoint if it has one.

If you run the server

Move long work to a background job (202 + polling), or serve that endpoint from a subdomain not proxied by Cloudflare.

Should you retry?

Yes, but the operation may have completed; check before retrying writes.

Example response

HTTP

HTTP/1.1 524 A Timeout Occurred
Content-Type: application/problem+json

{
  "type": "about:blank",
  "title": "A Timeout Occurred",
  "status": 524,
  "detail": "Cloudflare connected to the origin, but it didn't respond within 100 seconds."
}

Defined in: Cloudflare (non-standard). 524 is a server error: the problem is on the server's side.

Debugging an API call? Convert your request with the cURL converter, check the response with the JSON formatter, or see whether the API is down on its status page.

Often confused with

HTTP 524 FAQ

What does HTTP 524 mean?

524 A Timeout Occurred: Cloudflare connected to the origin, but it didn't respond within 100 seconds. The origin accepted the connection but took too long to send a response, usually because of a slow script or query.

Is 524 a client or server error?

It's a server error (5xx): the server failed to handle a valid request, so the fix is usually on the server's side.

How do I fix a 524 error?

Retry; for slow operations, use the API's async or export endpoint if it has one.

Should I retry after a 524?

Yes, but the operation may have completed; check before retrying writes.

Other 5xx status codes

All HTTP status codes