diff --git a/CMake/ITKExternalData.cmake b/CMake/ITKExternalData.cmake
index f071731df0d..93e56ecc00a 100644
--- a/CMake/ITKExternalData.cmake
+++ b/CMake/ITKExternalData.cmake
@@ -59,8 +59,6 @@ if(NOT ITK_FORBID_DOWNLOADS)
     "https://ipfs.filebase.io/ipfs/%(hash)"
     # Gateway for data pinned on pinata
     "https://gateway.pinata.cloud/ipfs/%(hash)"
-    # Cloudflare gateway
-    "https://cloudflare-ipfs.com/ipfs/%(hash)"
     # Additional gateway (modern but has redirect)
     "https://dweb.link/ipfs/%(hash)"
     # Data published on Girder
diff --git a/Documentation/docs/contributing/upload_binary_data.md b/Documentation/docs/contributing/upload_binary_data.md
index fa08fe7978b..78c41c15156 100644
--- a/Documentation/docs/contributing/upload_binary_data.md
+++ b/Documentation/docs/contributing/upload_binary_data.md
@@ -49,7 +49,7 @@ locations so it can be retrieved from any of the following at build time:
 
 - [Filebase] IPFS gateway (where uploads land)
 - [ITKTestingData] GitHub Pages mirror
-- Public IPFS HTTP gateways (`ipfs.io`, `dweb.link`, `cloudflare-ipfs.com`,
+- Public IPFS HTTP gateways (`ipfs.io`, `dweb.link`,
   `gateway.pinata.cloud`)
 - Local [Kubo] gateway (typically `127.0.0.1:8080`) when present
 - Kitware's Apache HTTP Server
diff --git a/Utilities/Maintenance/ExternalDataUpload/README.md b/Utilities/Maintenance/ExternalDataUpload/README.md
index 0641a1c52c5..1fad3e21d00 100644
--- a/Utilities/Maintenance/ExternalDataUpload/README.md
+++ b/Utilities/Maintenance/ExternalDataUpload/README.md
@@ -9,7 +9,7 @@ committed to the ITK source tree.
 This complements [`CMake/ITKExternalData.cmake`](../../../CMake/ITKExternalData.cmake),
 which fetches content at test configure time from the gateways listed there
 (`ITKTestingData` on GitHub Pages, local Kubo
-gateway, `ipfs.filebase.io`, `ipfs.io`, `gateway.pinata.cloud`, `cloudflare-ipfs.com`,
+gateway, `ipfs.filebase.io`, `ipfs.io`, `gateway.pinata.cloud`,
 `dweb.link`).
 
 ## How the upload works
@@ -250,7 +250,7 @@ ITK's CMake layer recognises the `.cid` extension via
 [`CMake/ITKExternalData.cmake`](../../../CMake/ITKExternalData.cmake). At
 configure time, `ExternalData.cmake` substitutes the CID into each
 `ExternalData_URL_TEMPLATES` entry (local Kubo gateway, `ipfs.io`,
-`gateway.pinata.cloud`, `cloudflare-ipfs.com`, `dweb.link`, plus the
+`gateway.pinata.cloud`, `dweb.link`, plus the
 `ITKTestingData` GitHub Pages mirror) and downloads from the first one that
 responds. The downloaded content is cached in
 `ExternalData_OBJECT_STORES` under `cid/<cid>`.
diff --git a/Utilities/Maintenance/ExternalDataUpload/SKILL.md b/Utilities/Maintenance/ExternalDataUpload/SKILL.md
index 79037c4ad64..82357df7208 100644
--- a/Utilities/Maintenance/ExternalDataUpload/SKILL.md
+++ b/Utilities/Maintenance/ExternalDataUpload/SKILL.md
@@ -157,7 +157,7 @@ Commit the ITK changes with an appropriate prefix per
 A `.cid` file is one line of plain text: a CIDv1, base32-encoded. ITK's
 `CMake/ITKExternalData.cmake` recognises the `.cid` extension and fetches
 through the gateway list declared there (local Kubo, `ipfs.io`,
-`gateway.pinata.cloud`, `cloudflare-ipfs.com`, `dweb.link`, plus the
+`gateway.pinata.cloud`, `dweb.link`, plus the
 `ITKTestingData` GitHub Pages mirror at
 `insightsoftwareconsortium.github.io/ITKTestingData/CID/<cid>`).