---
title: "Cloudflare Error 524: causes and how to fix it"
description: "Cloudflare connected to the origin successfully, but the origin took longer than 100 seconds to send a complete response. The request is too slow, not…"
canonical: "https://lemwatch.com/errors/cloudflare-524"
source: "https://lemwatch.com"
---

# Cloudflare Error 524: A timeout occurred while waiting for the origin

> Cloudflare connected to the origin successfully, but the origin took longer than 100 seconds to send a complete response. The request is too slow, not unreachable.

## Short answer

 Cloudflare connected to the origin successfully, but the origin took longer than 100 seconds to send a complete response. The request is too slow, not unreachable.

## What Cloudflare Error 524 means

 524 is a response-time limit, not a connection failure. It fires on long-running requests: heavy reports, unbatched imports, slow third-party API calls inside the request path.

## Causes and fixes, most likely first

- A single request genuinely takes longer than 100 seconds. Move the work to a background job and return immediately with a status the client can poll. Long synchronous requests are fragile regardless of the CDN.
- A slow external API call blocks the response. Set an aggressive timeout on outbound calls and degrade gracefully rather than blocking the whole response.
- Database queries without indexes are slow under load. Profile the slow endpoint and add the missing indexes. 524s that appear only at peak are usually query-plan problems.

## Cloudflare Error 524 on specific platforms

- Cloudflare Error 524 on WordPress — Cloudflare closes the connection after 100 seconds. Long WordPress jobs — imports, backups, WooCommerce reports — exceed that even though…

## How to stop it happening again

- Alert on response time approaching the CDN's limit, not just on the eventual failure.
- Never put long-running work in a synchronous request path.

## Check your own domain

 An external probe reports actual response time, which tells you how close normal requests are running to the limit before they tip over.

## Frequently asked questions

### Can I raise the 524 timeout?

 Enterprise plans can extend it, but the durable fix is making the request finish faster or moving the work to a background job.


## Related

- [All website error codes](https://lemwatch.com/errors)
- [Cloudflare Error 522](https://lemwatch.com/errors/cloudflare-522)
- [ERR_CONNECTION_TIMED_OUT](https://lemwatch.com/errors/err-connection-timed-out)
- [HTTP 504](https://lemwatch.com/http-status-codes/504)
- [HTTP 408](https://lemwatch.com/http-status-codes/408)
- [Free Uptime & response check](https://lemwatch.com/tools/website-uptime)
- [Cloudflare Error 524 on WordPress](https://lemwatch.com/errors/cloudflare-524/in-wordpress)
- [Cloudflare Error 523: Origin is unreachable](https://lemwatch.com/errors/cloudflare-523)