Updates 5xx links (#22237)

angelampcosta · daisyfaithauma · commit 96ee4aa8fe34 · 2025-05-08T11:48:00.000+03:00
diff --git a/src/content/docs/cache/how-to/always-online.mdx b/src/content/docs/cache/how-to/always-online.mdx
@@ -22,7 +22,7 @@ When the Internet Archive integration is enabled, Cloudflare tells the Internet
 
 When Always Online with Internet Archive integration is enabled, visitors see a banner at the top of the webpage explaining they are visiting an archived version of the website. Visitors can select the Refresh button to check whether the origin has recovered and fresh content is available.
 
-When a visitor requests content for an offline website, Cloudflare returns an HTTP response status code in the range [520–527](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error), depending on the issue. These status codes indicate that the origin is unreachable.
+When a visitor requests content for an offline website, Cloudflare returns an HTTP response status code in the range [520–527](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/), depending on the issue. These status codes indicate that the origin is unreachable.
 
 When the Internet Archive integration is enabled, Cloudflare checks the archive and serves the most recently archived version of the page.
 
diff --git a/src/content/docs/cache/how-to/cache-rules/settings.mdx b/src/content/docs/cache/how-to/cache-rules/settings.mdx
@@ -304,7 +304,7 @@ Refer to [Create a cache rule via API](/cache/how-to/cache-rules/create-api/#exa
 
 #### Proxy Read Timeout (Enterprise-only)
 
-Defines a timeout value between two successive read operations to your origin server. The default value can be found in the [Connection limits](/fundamentals/reference/connection-limits/) table. If you are attempting to reduce [`HTTP 524`](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-524-a-timeout-occurred) errors because of timeouts from an origin server, try increasing this timeout value using the API endpoint below.
+Defines a timeout value between two successive read operations to your origin server. The default value can be found in the [Connection limits](/fundamentals/reference/connection-limits/) table. If you are attempting to reduce [`HTTP 524`](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/) errors because of timeouts from an origin server, try increasing this timeout value using the API endpoint below.
 
 <Details header="API information">
 
diff --git a/src/content/docs/cache/troubleshooting/always-online.mdx b/src/content/docs/cache/troubleshooting/always-online.mdx
@@ -28,7 +28,7 @@ There are limitations with the Always Online functionality:
    - Always Online has not initially crawled the website
 2. Cloudflare cannot show private content behind logins or handle form submission (POSTs) if your origin web server is offline.
 
-Always Online does not trigger for HTTP response codes such as [404](/support/troubleshooting/http-status-codes/4xx-client-error/#404-not-found), [503](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-503-service-temporarily-unavailable), or [500](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-500-internal-server-error) errors such as database connection errors or internal server errors.
+Always Online does not trigger for HTTP response codes such as [404](/support/troubleshooting/http-status-codes/4xx-client-error/#404-not-found), [503](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-503/), or [500](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-500/) errors such as database connection errors or internal server errors.
 
 ## Frequently asked questions
 
diff --git a/src/content/docs/cloudflare-one/faq/troubleshooting.mdx b/src/content/docs/cloudflare-one/faq/troubleshooting.mdx
@@ -59,7 +59,7 @@ If none of the above scenarios apply, contact Cloudflare support with the follow
 - URL of the request
 - Screenshot or copy/paste of the content from the error page
 
-For more troubleshooting information, refer to [Support](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-526-invalid-ssl-certificate).
+For more troubleshooting information, refer to [Support](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/).
 
 ## I see an error in the Gateway Overview page, and no analytics are displayed.
 
diff --git a/src/content/docs/ddos-protection/managed-rulesets/adaptive-protection.mdx b/src/content/docs/ddos-protection/managed-rulesets/adaptive-protection.mdx
@@ -48,7 +48,7 @@ Cloudflare’s network is built to automatically monitor and mitigate large DDoS
 - For zones on any plan, Cloudflare will apply mitigations when the HTTP error rate is above the _High_ (default) sensitivity level of 1,000 errors-per-second rate threshold. You can decrease the sensitivity level by [configuring the HTTP DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/http/configure-dashboard/).
 - For zones on Pro, Business, and Enterprise plans, Cloudflare performs an additional check for better detection accuracy: the errors-per-second rate must also be at least five times the normal origin traffic levels before applying DDoS mitigations.
 
-Cloudflare determines the error rate based on all HTTP errors in the 52X range (Internal Server Error) and in the 53X range, except for [error 530](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-530). Currently, for DDoS mitigations based on HTTP error rate, you cannot exclude specific HTTP error codes.
+Cloudflare determines the error rate based on all HTTP errors in the 52X range (Internal Server Error) and in the 53X range, except for [error 530](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-530). Currently, for DDoS mitigations based on HTTP error rate, you cannot exclude specific HTTP error codes.
 
 For more information on the types of DDoS attacks covered by Cloudflare's DDoS protection, refer to [DDoS attack coverage](/ddos-protection/about/attack-coverage/).
 
diff --git a/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx b/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx
@@ -55,7 +55,7 @@ This rule is available for zones on any plan.
 
 The rule is adaptive for zones on the Pro, Business, or Enterprise plan. It performs an additional check for better detection accuracy: the errors-per-second rate must also be at least five times the normal traffic levels.
 
-All HTTP errors in the 52x range (Internal Server Error) and all errors in the 53x range excluding [530](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-530) are considered when factoring in the error rate.
+All HTTP errors in the 52x range (Internal Server Error) and all errors in the 53x range excluding [530](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-530) are considered when factoring in the error rate.
 
 ## Availability
 
diff --git a/src/content/docs/fundamentals/reference/connection-limits.mdx b/src/content/docs/fundamentals/reference/connection-limits.mdx
@@ -24,12 +24,12 @@ If you are using [Cloudflare tunnels](/cloudflare-one/connections/connect-networ
 
 | Type                                                                                      | Limit (seconds) | HTTP status code at limit                                                                                                              | [Configurable](/fundamentals/reference/connection-limits/#configurable-limits) |
 | ----------------------------------------------------------------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
-| <GlossaryTooltip term="TCP three-way handshake">Complete TCP Connection</GlossaryTooltip> | 15              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-522-connection-timed-out)                | No                                                                             |
-| <GlossaryTooltip term="ACK (Acknowledge)">TCP ACK</GlossaryTooltip> Timeout               | 90              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-522-connection-timed-out)                | No                                                                             |
-| <GlossaryTooltip term="TCP Keep-Alive">TCP Keep-Alive</GlossaryTooltip> Interval          | 30              | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error) | No                                                                             |
-| <GlossaryTooltip term="idle connection">Proxy Idle</GlossaryTooltip> Timeout              | 900             | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error) | No                                                                             |
-| <GlossaryTooltip term="proxy read timeout">Proxy Read Timeout</GlossaryTooltip>           | 100             | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-524-a-timeout-occurred)                  | [Yes](/api/resources/zones/subresources/settings/methods/edit/)                       |
-| <GlossaryTooltip term="proxy write timeout">Proxy Write Timeout</GlossaryTooltip>         | 30              | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-524-a-timeout-occurred)                  | No                                                                             |
+| <GlossaryTooltip term="TCP three-way handshake">Complete TCP Connection</GlossaryTooltip> | 15              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/)                | No                                                                             |
+| <GlossaryTooltip term="ACK (Acknowledge)">TCP ACK</GlossaryTooltip> Timeout               | 90              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/)                | No                                                                             |
+| <GlossaryTooltip term="TCP Keep-Alive">TCP Keep-Alive</GlossaryTooltip> Interval          | 30              | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/)                | No                                                                             |
+| <GlossaryTooltip term="idle connection">Proxy Idle</GlossaryTooltip> Timeout              | 900             | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/)                | No                                                                             |
+| <GlossaryTooltip term="proxy read timeout">Proxy Read Timeout</GlossaryTooltip>           | 100             | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/)                | [Yes](/api/resources/zones/subresources/settings/methods/edit/)                       |
+| <GlossaryTooltip term="proxy write timeout">Proxy Write Timeout</GlossaryTooltip>         | 30              | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/)                | No                                                                             |
 | HTTP/2 Pings to Origin                                                                    | Off             | -                                                                                                                                      | Yes                                                                            |
 | <GlossaryTooltip term="idle connection">HTTP/2 Connection Idle</GlossaryTooltip>          | 900             | No                                                                                                                                     | No                                                                             |
 
diff --git a/src/content/docs/pages/configuration/custom-domains.mdx b/src/content/docs/pages/configuration/custom-domains.mdx
@@ -41,7 +41,7 @@ If your site is already managed as a Cloudflare zone, the CNAME record will be a
 
 :::note
 
-To ensure a custom domain is added successfully, you must go through the [Add a custom domain](#add-a-custom-domain) process described above. Manually adding a custom CNAME record pointing to your Cloudflare Pages site - without first associating the domain (or subdomains) in the Cloudflare Pages dashboard - will result in your domain failing to resolve at the CNAME record address, and display a [`522` error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-522-connection-timed-out).
+To ensure a custom domain is added successfully, you must go through the [Add a custom domain](#add-a-custom-domain) process described above. Manually adding a custom CNAME record pointing to your Cloudflare Pages site - without first associating the domain (or subdomains) in the Cloudflare Pages dashboard - will result in your domain failing to resolve at the CNAME record address, and display a [`522` error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/).
 
 :::
 
diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/full-strict.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/full-strict.mdx
@@ -45,7 +45,7 @@ Before enabling **Full (strict)** mode, make sure your origin:
 - Allows HTTPS connections on port `443`.
 - Presents a certificate matching the requirements above.
 
-Otherwise, your visitors may experience a [526 error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-526-invalid-ssl-certificate).
+Otherwise, your visitors may experience a [526 error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/).
 
 ### Process
 
diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx
@@ -34,7 +34,7 @@ In addition to **Full** encryption, you can also set up [Authenticated Origin Pu
 
 ### Prerequisites
 
-Before enabling **Full** mode, make sure your origin allows HTTPS connections on port 443 and presents a certificate (self-signed, [Cloudflare Origin CA](/ssl/origin-configuration/origin-ca/), or purchased from a Certificate Authority). Otherwise, your visitors may experience a [525 error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-525-ssl-handshake-failed).
+Before enabling **Full** mode, make sure your origin allows HTTPS connections on port 443 and presents a certificate (self-signed, [Cloudflare Origin CA](/ssl/origin-configuration/origin-ca/), or purchased from a Certificate Authority). Otherwise, your visitors may experience a [525 error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525/).
 
 <Render file="ssl-mode-errors" />
 
diff --git a/src/content/docs/support/third-party-software/others/configure-cloudflare-and-heroku-over-https.mdx b/src/content/docs/support/third-party-software/others/configure-cloudflare-and-heroku-over-https.mdx
@@ -111,6 +111,6 @@ Server: cloudflare
 CF-RAY: 3e1e77d5c42b8c52-SFO-DOG
 ```
 
-If SSL was not working for your domain (for example, your SSL certificate has not yet been issued), you would see a [525](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-525-ssl-handshake-failed) or [526](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-526-invalid-ssl-certificate) HTTP response after the redirect.
+If SSL was not working for your domain (for example, your SSL certificate has not yet been issued), you would see a [525](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525/) or [526](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-526/) HTTP response after the redirect.
 
 Please note that the issuing of a Universal SSL certificate typically takes up to 24 hours. Our paid SSL certificates issue within 10-15 minutes.
diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx
@@ -465,7 +465,7 @@ Please refer to this documentation, which explains more about analysing MTR: [Ho
 
 Issues that happen at the layers 3/4 occur before requests reaching Cloudflare's logging system, so they do not show up in the HTTP logs. Therefore, troubleshooting issues related to connection resets, packet loss or SSL handshake failures can be tricky without a deep investigation at the packet level.
 
-Some HTTP errors generated by Cloudflare, such as [520s](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error), [524s](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-524-a-timeout-occurred) and [525s](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-525-ssl-handshake-failed), show underlying issues at layers 3/4, and might require a packet capture for further investigation.
+Some HTTP errors generated by Cloudflare, such as [520s](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-520/), [524s](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/) and [525s](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-525/), show underlying issues at layers 3/4, and might require a packet capture for further investigation.
 
 **How to Run a Packet Capture**
 
diff --git a/src/content/docs/support/troubleshooting/http-status-codes/1xx-informational.mdx b/src/content/docs/support/troubleshooting/http-status-codes/1xx-informational.mdx
@@ -49,4 +49,4 @@ The 102 Processing status code is commonly used in scenarios requiring long-runn
 
 ### Cloudflare-specific information
 
-If Cloudflare receives a 102 Processing response, it expects a final response within 100 seconds. Failure to receive this response results in an [Error 522: Connection Timed Out](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-522-connection-timed-out). However, sending interim 102 Processing responses can help prevent [Error 524: A timeout occurred](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-524-a-timeout-occurred), ensuring that the connection remains active while the server processes the request.
+If Cloudflare receives a 102 Processing response, it expects a final response within 100 seconds. Failure to receive this response results in an [Error 522: Connection Timed Out](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/). However, sending interim 102 Processing responses can help prevent [Error 524: A timeout occurred](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/), ensuring that the connection remains active while the server processes the request.
diff --git a/src/content/docs/workers-ai/guides/tutorials/build-a-retrieval-augmented-generation-ai.mdx b/src/content/docs/workers-ai/guides/tutorials/build-a-retrieval-augmented-generation-ai.mdx
@@ -590,7 +590,7 @@ Preview your Worker at `<YOUR_WORKER>.<YOUR_SUBDOMAIN>.workers.dev`.
 
 :::note[Note]
 
-When pushing to your `*.workers.dev` subdomain for the first time, you may see [`523` errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-523-origin-is-unreachable) while DNS is propagating. These errors should resolve themselves after a minute or so.
+When pushing to your `*.workers.dev` subdomain for the first time, you may see [`523` errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-523/) while DNS is propagating. These errors should resolve themselves after a minute or so.
 
 :::
 
diff --git a/src/content/docs/workers/get-started/guide.mdx b/src/content/docs/workers/get-started/guide.mdx
@@ -191,7 +191,7 @@ Preview your Worker at `<YOUR_WORKER>.<YOUR_SUBDOMAIN>.workers.dev`.
 
 <Details header="Seeing 523 errors?">
 
-If you see [`523` errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-523-origin-is-unreachable) when pushing your `*.workers.dev` subdomain for the first time, wait a minute or so and the errors will resolve themselves.
+If you see [`523` errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-523/) when pushing your `*.workers.dev` subdomain for the first time, wait a minute or so and the errors will resolve themselves.
 
 </Details>
 
diff --git a/src/content/docs/workers/languages/rust/index.mdx b/src/content/docs/workers/languages/rust/index.mdx
@@ -142,7 +142,7 @@ Preview your Worker at `<YOUR_WORKER>.<YOUR_SUBDOMAIN>.workers.dev`.
 
 :::note
 
-When pushing to your `*.workers.dev` subdomain for the first time, you may see [`523` errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-523-origin-is-unreachable) while DNS is propagating. These errors should resolve themselves after a minute or so.
+When pushing to your `*.workers.dev` subdomain for the first time, you may see [`523` errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-523/) while DNS is propagating. These errors should resolve themselves after a minute or so.
 
 :::
 
diff --git a/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx b/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx
@@ -3,4 +3,4 @@
 
 ---
 
-Zero-downtime failover will trigger a single retry only if there is another healthy endpoint in the pool and a [521, 522, 523, 525 or 526 error code](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-521-web-server-is-down) is occurring. No other error codes will trigger a zero-downtime failover operation.
+Zero-downtime failover will trigger a single retry only if there is another healthy endpoint in the pool and a [521, 522, 523, 525 or 526 error code](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-521/) is occurring. No other error codes will trigger a zero-downtime failover operation.
