From 42b5b67d799c2de2f5a334f19585dd081f367355 Mon Sep 17 00:00:00 2001
From: Duncan-Cloudflare <118954567+Duncan-Cloudflare@users.noreply.github.com>
Date: Thu, 16 Jan 2025 19:04:40 +1100
Subject: [PATCH] Update troubleshooting-cloudflare-5xx-errors.mdx

SPM-2669
---
 .../cloudflare-errors/troubleshooting-cloudflare-5xx-errors.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors.mdx b/src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors.mdx
index 54235a407b7ab3..c688913dd259f2 100644
--- a/src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors.mdx
+++ b/src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors.mdx
@@ -246,7 +246,7 @@ If none of the above leads to a resolution, request the following information fr
 
 Error 524 usually indicates that Cloudflare successfully connected to the origin web server, but the origin did not provide an HTTP response before the default 100 seconds [Proxy Read Timeout](/fundamentals/reference/connection-limits/). This can happen if the origin server is taking too long because it has too much work to do, for example, a large data query, or because the server is struggling for resources and cannot return any data in time.
 
-Error 524 can also indicate that Cloudflare successfully connected to the origin web server to write data, but the write did not complete before the 30 seconds [Proxy Write Timeout](/fundamentals/reference/connection-limits/).
+Error 524 can also indicate that Cloudflare successfully connected to the origin web server to write data, but the write did not complete before the 30 seconds [Proxy Write Timeout](/fundamentals/reference/connection-limits/) (or 6.5 seconds in the case of [Cloudflare Images](https://developers.cloudflare.com/images/)).
 
 :::note