---
title: "524 A Timeout Occurred"
canonical: "https://lemwatch.com/http-status-codes/524"
category: "server-error"
last_verified: "2026-08-11"
source: "https://lemwatch.com"
---

# HTTP 524 A Timeout Occurred

**Summary** — Cloudflare established a TCP connection to the origin but the origin did not reply with an HTTP response in time.

## What it means

HTTP 524 is a Cloudflare-specific error. The TCP connection was established (unlike 522), but the origin server took too long to send an HTTP response. Cloudflare's default timeout is 100 seconds for free plans.

## Common causes

- Long-running server processes
- Slow database queries
- Large file generation
- Application timeout

## How to fix

- Optimise slow server-side operations
- Use Cloudflare Enterprise for longer timeouts
- Implement async processing for long operations
- Add loading indicators for slow pages

## SEO impact

Slow pages that timeout hurt user experience and rankings. Google prefers fast-loading pages.

## Monitoring tip

LemWatch tracks response times and can warn you when pages are approaching Cloudflare's timeout threshold.

**Related:** [504](https://lemwatch.com/http-status-codes/504.md), [522](https://lemwatch.com/http-status-codes/522.md)

_Canonical HTML page: https://lemwatch.com/http-status-codes/524_