Opens in a new tab

Cloudflare error 524: A timeout occurred

Cloudflare connected to your server and sent the request, but no response came back within its read timeout — 125 seconds. Something on the server is taking too long: a long-running script, a heavy database query, or a server too overloaded to answer in time.

A timeout occurred
Error code 524
How 2 other clients word the same error

Browser tab

example.com | 524: A timeout occurred

curl -I

HTTP/2 524
ErrorError 524: A timeout occurred
Usually fixed byThe site owner or host
Status524 — Cloudflare’s own code
Read timeout125 seconds (100 until October 2025, then 120); Enterprise plans can raise it to 6,000
Write timeout30 seconds, not adjustable

Check the site from outside

Enter the address: we load it from our network and show the status code, how long it took, and the error if it failed.

What it means

Once the connection is made, Cloudflare waits for the server’s response — the Proxy Read Timeout. If nothing arrives within 125 seconds, it stops waiting and shows 524. The server may well finish the work later; the visitor never sees it. A 524 can also mean the request itself could not be written to the server within 30 seconds.

Why it happens

  • A script that runs for minutes — an import, an export, a report, a backup started from the browser.
  • A slow database query, or a database locked by another one.
  • A server overloaded by traffic or by background tasks, answering every request slowly.

How to fix it

  1. Find what is slow: the web server’s slow log, PHP-FPM’s slow log, the database’s slow query log.
  2. Move long jobs out of the web request: run them in the background and let the page poll for the result.
  3. Serve long-running tools from a subdomain whose DNS record is set to DNS only, so Cloudflare’s timeout does not apply.
  4. On an Enterprise plan, raise the timeout (up to 6,000 seconds) with a Cache Rule or the zone’s proxy_read_timeout setting.

If you are visiting the site

  • Nothing on your side causes it. The request may still be running on the server, so do not resubmit a form or a payment straight away.

See it for yourself

curl -s -o /dev/null -w 'first byte after %{time_starttransfer}s\n' https://example.com/slow-page --resolve example.com:443:203.0.113.10

With the origin’s IP in place of 203.0.113.10: curl skips Cloudflare and prints how long the server itself takes to start answering.

Sources

Error text and meaning checked on 25 September 2026 against these official sources:

Know when your site goes down — before your visitors do

Add your site and we check it every few minutes, confirm a failure from another location — Europe, North America or Asia — before calling it down, and email you when it stops answering and when it is back. Free for two sites.

Create a free account