HTTP status code

Cloudflare error 524 A Timeout Occurred

Cloudflare 524 means the connection to the origin succeeded, but the server didn't return a response within 100 seconds.

Reviewed: 6 November 2026
Class
52x · Cloudflare
Where the problem is
Problem between Cloudflare and the origin server
Who fixes it
The site owner has to fix it (origin server).

What it means

By default Cloudflare waits 100 seconds for the origin server to respond. If the application doesn't return a response in that time, a 524 is shown. It's typical of long exports, reports, imports or slow queries.

Most common causes

  • A long-running task in the application (export, import, report generation).
  • A slow database query.
  • An overloaded origin server.
  • Locking or waiting on an external service.

What you can do as a visitor

  1. Try again later. For exports, try a smaller data range.

Shows the HTTP status, redirect chain, HTTPS and basic SEO signals. Works for public addresses only.

What the site owner or developer should do

  1. Run long tasks asynchronously (job queue) and deliver the result by email or notification.
  2. Optimise queries and add indexes.
  3. For long-running endpoints, use a subdomain that bypasses the Cloudflare proxy (grey cloud), or the Enterprise timeout setting.

Impact on SEO and Google

A 524 usually affects backend functions; if it appears on public pages, it points to serious slowness.

Frequently asked questions

Can I extend the 100 seconds?

Not on the Free and Pro plans; on Enterprise, yes. It's better to run the task asynchronously.

524 or 504?

Both mean a timeout. 524 is specific to Cloudflare.

Sources