Error 524: A Timeout Occurred

The short version: Reload after a minute: a 524 sits on the website's side and you cannot fix it as a visitor. It means Cloudflare connected to the origin but got no HTTP response within 125 seconds. Run the website yourself? Find the slow request. Raising the timeout is only possible on Enterprise, and it does not make the work any faster.

Key takeaways

• Cloudflare connected to your origin successfully, then waited for an HTTP response that never came. The default Proxy Read Timeout is 125 seconds.
• This is the website's problem, not yours. As a visitor there is nothing to fix beyond waiting and reloading.
• A 524 is the most informative of the Cloudflare 5xx codes: the network path works, the server is up, and the application itself is too slow. That narrows the search to your own code and queries.
• A separate 30 second Proxy Write Timeout also returns 524, and unlike the read timeout it cannot be adjusted on any plan.
• Only Enterprise zones can raise the 125 second limit, up to 6,000 seconds. On every other plan the answer is to make the request faster or move it off the proxied path.

Error type

Cloudflare 5xx edge error

Whose side

Always the website

Fix difficulty

Moderate (website owner)

Common cause

Origin connected but responded too slowly

What does Error 524: A Timeout Occurred mean?

A 524 A Timeout Occurred is a Cloudflare-specific status code that appears when Cloudflare opened a connection to your origin server successfully, but the origin did not return an HTTP response inside the Proxy Read Timeout, which defaults to 125 seconds.

That makes a 524 unusually specific. The network path works, the firewall is not in the way, and the server accepted the request. Something in the application, most often a query or an external call, is simply taking too long. As a visitor there is nothing to fix.

524

Cloudflare status code

125s

Default Proxy Read Timeout

30s

Proxy Write Timeout (fixed)

6,000s

Enterprise maximum

How the Error 524: A Timeout Occurred error appears

The wording changes depending on your browser, device, or server. Here is how this error commonly shows up:

example.com

524

A timeout occurred

The origin took too long to respond.

• Error 524: a timeout occurred
• Error 524 Cloudflare
• HTTP 524
• Cloudflare 524 origin time-out
• A timeout occurred Error code 524
• Origin Time-out

524 vs 522, 521 and 504

These four look alike on an error page and mean quite different things. The distinction is how far the request got before something gave up.

Cloudflare timeouts that return a 524

Two different limits produce this code, and only one of them can be changed. Knowing which fired tells you whether to optimise a read or a write path.

Where the 524 limit sits against other timeouts

Cloudflare is rarely the tightest timer in the stack. If a shorter one fires first you get a different code, which is why a 524 specifically implies everything below it waited longer.

What causes Error 524: A Timeout Occurred?

• A long-running process at the origin, such as a large data export, a report build, or a bulk import.
• A slow or unindexed database query that holds the request open past the timeout.
• An overloaded origin that is struggling for resources and cannot return anything in time.
• A blocking call to a slow external API, where your response time inherits someone else's.
• A write that does not complete inside the fixed 30 second Proxy Write Timeout, for example a large upload.
• A deadlock or lock contention in the application that leaves the request waiting indefinitely.

How to find the cause fast

1. Reload once after a minute, then check whether the whole site or only one page fails. A 524 confined to a single URL is an application problem, not an outage.
2. Owners: time the request with curl -w "%{time_starttransfer}" -o /dev/null -s https://yourdomain.com/slow-page. Anything approaching 125 seconds is the culprit.
3. Request the origin directly, bypassing Cloudflare. If the origin also takes over two minutes, Cloudflare is reporting the problem accurately rather than causing it.
4. Enable origin response time logging and find the slowest endpoints. Requests whose 95th percentile sits near the timeout will start returning 524s under any extra load.
5. Check whether the work completes server-side after the visitor got the error. That distinguishes a slow request from one that hangs forever, and they have different fixes.

Terminal

curl -sI -w "%{time_total}s\n" https://example.com/reportHTTP/1.1 524 Origin Time-out125.4s# the origin answered the connection, then went quiet# compare against the origin directly to confirm it is the app, not the path

How Error 524: A Timeout Occurred looks from the outside

A 524 arrives as a complete HTTP response from the Cloudflare edge, but unlike a 521 or 522 it arrives slowly, roughly two minutes after the request began. An external check therefore records both a 524 status and a response time near the timeout, and that pairing is the diagnosis: the origin was reachable the whole time and simply never answered. Because 524s often affect one heavy endpoint rather than the homepage, monitoring the specific URL that does the expensive work catches this long before a check of the front page would.

To confirm the exact code a URL returns, or to re-test several at once after a fix, run them through the free bulk URL status checker.

How to fix Error 524: A Timeout Occurred

If you are a visitor

1. Wait a minute and reload. A 524 caused by a temporary spike often clears on its own.
2. If only one page fails while the rest of the site works, the problem is that specific page. Nothing on your side will change it.
3. Check whether it is down for everyone with Is Website Down?
4. There is nothing to fix on your device. The request reached the website and the website was too slow to answer.

If you run the website

1. Find the slow request first. Origin response time logs, an APM trace, or a slow query log will name it faster than any configuration change.
2. Optimise the underlying work: add the missing index, cache the expensive result, or batch the query that walks the whole table.
3. Move genuinely long processes off the proxied path. Cloudflare recommends a DNS-only (grey-clouded) subdomain for requests that legitimately run past 125 seconds.
4. Better still, restructure long work as a background job that returns immediately and reports progress by polling. That removes the timeout question entirely.
5. On Enterprise, you can raise the Proxy Read Timeout up to 6,000 seconds with a Cache Rule or the zone settings API. On every other plan this option does not exist.
6. Remember the 30 second Proxy Write Timeout is fixed. If large uploads are failing, the fix is chunking them, not a setting.

Still not fixed? Next steps

• A 524 that only affects one endpoint is an application problem, not an infrastructure one. Profile that request rather than adjusting any timeout.
• If the slow work is legitimate, such as a large export or report, move it behind a DNS-only (grey-clouded) subdomain so it never passes through the proxy, or restructure it as a background job with status polling.
• Check whether the origin finished the work after Cloudflare gave up. A request that completes at 140 seconds server-side while the visitor saw a 524 at 125 confirms the timeout rather than a hang, and points at optimisation instead of a crash.
• On a managed stack, give your host the affected URL and exact timestamps. Origin response time logging is what settles which request is slow, and most hosts can enable it on request.

Code & configuration

Copy-paste starting points. Replace example.com and the paths with your own, and test changes on staging before production.

Find the slow endpoint before changing any timeout

# time the full request, and time to first byte
curl -o /dev/null -s -w "connect: %{time_connect}s\nttfb: %{time_starttransfer}s\ntotal: %{time_total}s\n" \
  https://example.com/slow-report

# MySQL: log anything slower than 5 seconds
SET GLOBAL slow_query_log = 1;
SET GLOBAL long_query_time = 5;

How to prevent Error 524: A Timeout Occurred

A 524 rarely takes the whole site down. It hides on the one report, export, or search page that quietly got slower, which is exactly why it tends to be found by a customer rather than by you. Pulsetic checks any URL you choose, not just the homepage, from multiple locations as often as every 30 seconds, and records the response time alongside the status code. Point a check at the endpoint that does the expensive work and you will see the response time climbing toward the limit well before it starts returning 524s.

Learn how Pulsetic's uptime monitoring detects this from the outside, across 15+ locations.

Sources and further reading

The specifications and vendor documentation this guide is written from, plus deeper reading on the parts it only summarises.

• Cloudflare: Error 524 (a timeout occurred)
• nginx: proxy_read_timeout reference
• MDN: 504 Gateway Timeout
• RFC 9110: HTTP Semantics