---
title: "524 A Timeout Occurred — what it means and how to fix it"
description: "Cloudflare connected to the origin successfully but the origin did not finish responding in time. What causes an HTTP 524, what to try as a visitor, and what to check if it is your own site."
url: https://atoneplace.net/error/524/
site: "At One Place"
---

# HTTP 524 — A Timeout Occurred

**HTTP 524: A Timeout Occurred**

Cloudflare connected to the origin successfully but the origin did not finish responding in time.

## What 524 actually means

Cloudflare's own code, not part of HTTP — effectively their version of a 504. The TCP connection was established and the request was delivered, but the origin did not send a complete response within Cloudflare's proxy read timeout, which defaults to 125 seconds. It always means the origin is running but slow: a long query, a heavy report, or a request waiting on something that never came back.

## Common causes

- A request taking longer than Cloudflare's default 125-second proxy read timeout
- A slow database query or an unindexed table scan
- A long-running export, import or report generation done synchronously
- A WebSocket or long-polling connection idling past the timeout
- An origin waiting on a third-party API that never answers

## If you're just trying to view the page

1. Retry — if the operation is heavy, it may succeed when the server is less busy
2. If you triggered a large export or report, try a smaller range
3. Nothing else; the site's server needs to answer faster

## If it's your site

1. Move work that takes longer than a few seconds into a background job and return immediately with a status URL
2. Profile and fix the slow path — the 125-second timeout is not adjustable below Enterprise
3. Enterprise plans can raise the proxy read timeout as far as 6,000 seconds, but that is a workaround rather than a fix
4. For long-lived connections, use Cloudflare's WebSocket support rather than long-polling over plain HTTP
5. Consider routing the slow endpoint around Cloudflare on a grey-clouded (DNS-only) subdomain if it genuinely must run long

## Reference

- **Status code:** 524
- **Reason phrase:** A Timeout Occurred
- **Category:** 5xx — Server Error
- **Cacheable by default:** No

## Common questions

### What does HTTP 524 mean?

Cloudflare connected to the origin successfully but the origin did not finish responding in time. Cloudflare's own code, not part of HTTP — effectively their version of a 504. The TCP connection was established and the request was delivered, but the origin did not send a complete response within Cloudflare's proxy read timeout, which defaults to 125 seconds.

### How do I fix a 524 error?

Retry — if the operation is heavy, it may succeed when the server is less busy

### Is 524 a client error or a server error?

524 is in the 5xx range, which means server error. The request was acceptable but the server could not fulfil it, so retrying later can succeed.

## Related pages

- [500 Internal Server Error](https://atoneplace.net/error/500/)
- [502 Bad Gateway](https://atoneplace.net/error/502/)
- [503 Service Unavailable](https://atoneplace.net/error/503/)
- [504 Gateway Timeout](https://atoneplace.net/error/504/)
- [521 Web Server Is Down](https://atoneplace.net/error/521/)
- [522 Connection Timed Out](https://atoneplace.net/error/522/)
- [520 Web Server Returned an Unknown Error](https://atoneplace.net/error/520/)
- [525 SSL Handshake Failed](https://atoneplace.net/error/525/)
- [526 Invalid SSL Certificate](https://atoneplace.net/error/526/)
- [530 Origin DNS Error](https://atoneplace.net/error/530/)
- [501 Not Implemented](https://atoneplace.net/error/501/)
- [511 Network Authentication Required](https://atoneplace.net/error/511/)

## Sources

- Hypertext Transfer Protocol (HTTP) Status Code Registry — IANA (https://www.iana.org/assignments/http-status-codes/)
- RFC 9110: HTTP Semantics — IETF (https://www.rfc-editor.org/rfc/rfc9110.html)