HTTP 524 in Cloudflare

Origin took longer than 100s to send headers.

Why Cloudflare returns 524

Origin took longer than 100s to send headers.

How to fix it

Move the long task to a background queue, or upgrade to Enterprise for a longer timeout.

Where this surfaces in Cloudflare

The Cloudflare edge before your origin ever sees the request. Look at the Ray ID in the response.

Cloudflare — CDN, WAF, and edge network in front of your origin.

What HTTP 524 means generally

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

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.

Other common causes of 524

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

SEO impact

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

How to catch it next time

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