diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx
index 9c7e8e8758ef275..aed35077a54e918 100644
--- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx
+++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524.mdx
@@ -36,7 +36,7 @@ Contact your hosting provider or site administrator for assistance in adjusting
 
 Here are some other actions you can take on the Cloudflare side:
 
-- If you regularly run HTTP requests that take over 100 seconds to complete (for example, large data exports), move those processes behind a [subdomain not proxied (DNS-only, grey clouded)](/dns/proxy-status/#dns-only-records) in the Cloudflare **DNS** app.
+- If you regularly run HTTP requests that take over 120 seconds to complete (for example, large data exports), move those processes behind a [subdomain not proxied (DNS-only, grey clouded)](/dns/proxy-status/#dns-only-records) in the Cloudflare **DNS** app.
 - Enterprise customers can increase the `524` timeout up to 6,000 seconds:
   - If your content can be cached, you can create a [Cache Rule](/cache/how-to/cache-rules/settings/#proxy-read-timeout-enterprise-only) with the `Proxy Read Timeout` setting.
   - You can increase the `proxy_read_timeout` setting for the whole zone using the using the [Edit zone setting API endpoint](/api/resources/zones/subresources/settings/methods/edit/).