diff --git a/website/src/pages/ar/indexing/new-chain-integration.mdx b/website/src/pages/ar/indexing/new-chain-integration.mdx
index b204d002b25d..72982bb33995 100644
--- a/website/src/pages/ar/indexing/new-chain-integration.mdx
+++ b/website/src/pages/ar/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 
diff --git a/website/src/pages/ar/indexing/overview.mdx b/website/src/pages/ar/indexing/overview.mdx
index 200a3a6a64e5..50faf9406a27 100644
--- a/website/src/pages/ar/indexing/overview.mdx
+++ b/website/src/pages/ar/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/ar/indexing/tooling/graph-node.mdx b/website/src/pages/ar/indexing/tooling/graph-node.mdx
index edde8a157fd3..b535d6a471e7 100644
--- a/website/src/pages/ar/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/ar/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### IPFS Nodes
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Prometheus metrics server
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Getting started with Kubernetes
diff --git a/website/src/pages/ar/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/ar/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 2bc0ec5f514c..e3e3a7e3d455 100644
--- a/website/src/pages/ar/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/ar/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/ar/subgraphs/guides/near.mdx b/website/src/pages/ar/subgraphs/guides/near.mdx
index 04daec8b6ac7..ff812b4eee58 100644
--- a/website/src/pages/ar/subgraphs/guides/near.mdx
+++ b/website/src/pages/ar/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/ar/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/ar/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 17258dd13ea1..3b55aea5b072 100644
--- a/website/src/pages/ar/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/ar/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## Deployment ID
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/cs/indexing/new-chain-integration.mdx b/website/src/pages/cs/indexing/new-chain-integration.mdx
index 0d856bfa9374..71deffe8c79a 100644
--- a/website/src/pages/cs/indexing/new-chain-integration.mdx
+++ b/website/src/pages/cs/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 
diff --git a/website/src/pages/cs/indexing/overview.mdx b/website/src/pages/cs/indexing/overview.mdx
index 8acf4fdf72a9..6427052cb74a 100644
--- a/website/src/pages/cs/indexing/overview.mdx
+++ b/website/src/pages/cs/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/cs/indexing/tooling/graph-node.mdx b/website/src/pages/cs/indexing/tooling/graph-node.mdx
index 9257902fe247..cea77cebe157 100644
--- a/website/src/pages/cs/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/cs/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### IPFS uzly
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Metrický server Prometheus
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Začínáme s Kubernetes
diff --git a/website/src/pages/cs/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/cs/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 29c75273aa17..6a3f991fa0b6 100644
--- a/website/src/pages/cs/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/cs/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/cs/subgraphs/guides/near.mdx b/website/src/pages/cs/subgraphs/guides/near.mdx
index 275c2aba0fd4..6b0cddb546cf 100644
--- a/website/src/pages/cs/subgraphs/guides/near.mdx
+++ b/website/src/pages/cs/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/cs/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/cs/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 7792cb56d855..0b5e6bb15dc6 100644
--- a/website/src/pages/cs/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/cs/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## ID nasazení
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/de/indexing/new-chain-integration.mdx b/website/src/pages/de/indexing/new-chain-integration.mdx
index eed49796a99f..07d2bad6b390 100644
--- a/website/src/pages/de/indexing/new-chain-integration.mdx
+++ b/website/src/pages/de/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Die Konfiguration von Graph Node ist so einfach wie die Vorbereitung Ihrer lokal
 
    > Ändern Sie nicht den Namen der Env-Variable selbst. Er muss `ethereum` bleiben, auch wenn der Netzwerkname anders lautet.
 
-3. Führen Sie einen IPFS-Knoten aus oder verwenden Sie den von The Graph verwendeten: https://api.thegraph.com/ipfs/
+3. Führen Sie einen IPFS-Knoten aus oder verwenden Sie den von The Graph verwendeten: https://ipfs.thegraph.com
 
 ## Substreams-getriebene Subgraphen
 
diff --git a/website/src/pages/de/indexing/overview.mdx b/website/src/pages/de/indexing/overview.mdx
index 4635fbb7f2b9..3305ea5d4b2e 100644
--- a/website/src/pages/de/indexing/overview.mdx
+++ b/website/src/pages/de/indexing/overview.mdx
@@ -131,7 +131,7 @@ Im Zentrum der Infrastruktur eines Indexierers steht der Graph Node, der die ind
 
 - **Datenendpunkt** - Bei EVM-kompatiblen Netzwerken muss der Graph Node mit einem Endpunkt verbunden sein, der eine EVM-kompatible JSON-RPC-API bereitstellt. Dabei kann es sich um einen einzelnen Client handeln oder um ein komplexeres Setup, das die Last auf mehrere Clients verteilt. Es ist wichtig, sich darüber im Klaren zu sein, dass bestimmte Subgraphen besondere Client-Fähigkeiten erfordern, wie z. B. den Archivmodus und/oder die Paritätsverfolgungs-API.
 
-- **IPFS-Knoten (Version kleiner als 5)** - Die Metadaten für die Subgraph-Bereitstellung werden im IPFS-Netzwerk gespeichert. Der Graph Node greift in erster Linie auf den IPFS-Knoten während der Bereitstellung des Subgraphen zu, um das Subgraphen-Manifest und alle verknüpften Dateien zu holen. Netzwerk-Indizierer müssen keinen eigenen IPFS-Knoten hosten, ein IPFS-Knoten für das Netzwerk wird unter https://ipfs.network.thegraph.com gehostet.
+- **IPFS-Knoten (Version kleiner als 5)** - Die Metadaten für die Subgraph-Bereitstellung werden im IPFS-Netzwerk gespeichert. Der Graph Node greift in erster Linie auf den IPFS-Knoten während der Bereitstellung des Subgraphen zu, um das Subgraphen-Manifest und alle verknüpften Dateien zu holen. Netzwerk-Indizierer müssen keinen eigenen IPFS-Knoten hosten, ein IPFS-Knoten für das Netzwerk wird unter https://ipfs.thegraph.com gehostet.
 
 - **Indexierer-Dienst** - Erledigt alle erforderlichen externen Kommunikationen mit dem Netz. Teilt Kostenmodelle und Indizierungsstatus, leitet Abfrageanfragen von Gateways an einen Graph Node weiter und verwaltet die Abfragezahlungen über Statuskanäle mit dem Gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Erste Schritte mit Docker
diff --git a/website/src/pages/de/indexing/tooling/graph-node.mdx b/website/src/pages/de/indexing/tooling/graph-node.mdx
index 3c4cb903b165..0d4466c8642b 100644
--- a/website/src/pages/de/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/de/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ Während einige Subgraphen nur einen vollständigen Knoten benötigen, können e
 
 ### IPFS-Knoten
 
-Die Metadaten für den Einsatz von Subgraphen werden im IPFS-Netzwerk gespeichert. Der Graph Node greift während des Einsatzes von Subgraphen primär auf den IPFS-Knoten zu, um das Subgraphen-Manifest und alle verknüpften Dateien abzurufen. Netzwerkindizierer müssen keinen eigenen IPFS-Knoten hosten. Ein IPFS-Knoten für das Netzwerk wird auf https://ipfs.network.thegraph.com gehostet.
+Die Metadaten für den Einsatz von Subgraphen werden im IPFS-Netzwerk gespeichert. Der Graph Node greift während des Einsatzes von Subgraphen primär auf den IPFS-Knoten zu, um das Subgraphen-Manifest und alle verknüpften Dateien abzurufen. Netzwerkindizierer müssen keinen eigenen IPFS-Knoten hosten. Ein IPFS-Knoten für das Netzwerk wird auf https://ipfs.thegraph.com gehostet.
 
 ### Prometheus-Metrikserver
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Erste Schritte mit Kubernetes
diff --git a/website/src/pages/de/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/de/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 2fa5e3654038..474081f817d5 100644
--- a/website/src/pages/de/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/de/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/de/subgraphs/guides/near.mdx b/website/src/pages/de/subgraphs/guides/near.mdx
index 3bb7e5af4796..b28d11baf154 100644
--- a/website/src/pages/de/subgraphs/guides/near.mdx
+++ b/website/src/pages/de/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Sobald Ihr Subgraph erstellt wurde, können Sie ihn mit dem CLI-Befehl `graph de
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # erstellt einen Subgraph auf einem lokalen Graph-Knoten (bei Subgraph Studio wird dies über die Benutzeroberfläche erledigt)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # lädt die Build-Dateien auf einen angegebenen IPFS-Endpunkt hoch und stellt den Subgraphen dann auf der Grundlage des manifestierten IPFS-Hashs auf einem angegebenen Graph-Knoten bereit
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # lädt die Build-Dateien auf einen angegebenen IPFS-Endpunkt hoch und stellt den Subgraphen dann auf der Grundlage des manifestierten IPFS-Hashs auf einem angegebenen Graph-Knoten bereit
 ```
 
 Die Knotenkonfiguration hängt davon ab, wo der Subgraph eingesetzt werden soll.
diff --git a/website/src/pages/de/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/de/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index b35d7d952215..5d1e027a9f07 100644
--- a/website/src/pages/de/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/de/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Hier sind einige wichtige Unterschiede zwischen den beiden IDs: ![](/img/subgrap
 
 ## Einsatz-ID
 
-Die Bereitstellungs-ID ist der IPFS-Hash der kompilierten Manifestdatei, der auf andere Dateien im IPFS statt auf relative URLs auf dem Computer verweist. Auf das kompilierte Manifest kann zum Beispiel zugegriffen werden über: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. Um die Bereitstellungs-ID zu ändern, kann man einfach die Manifestdatei aktualisieren, z. B. durch Ändern des Beschreibungsfeldes, wie in der [Subgraph manifest documentation] (https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api) beschrieben.
+Die Bereitstellungs-ID ist der IPFS-Hash der kompilierten Manifestdatei, der auf andere Dateien im IPFS statt auf relative URLs auf dem Computer verweist. Auf das kompilierte Manifest kann zum Beispiel zugegriffen werden über: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. Um die Bereitstellungs-ID zu ändern, kann man einfach die Manifestdatei aktualisieren, z. B. durch Ändern des Beschreibungsfeldes, wie in der [Subgraph manifest documentation] (https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api) beschrieben.
 
 Wenn Abfragen unter Verwendung der Einsatz-ID eines Subgraphen durchgeführt werden, geben wir eine Version dieses Subgraphen zur Abfrage an. Die Verwendung der Bereitstellungs-ID zur Abfrage einer bestimmten Subgraphenversion führt zu einer ausgefeilteren und robusteren Einrichtung, da die volle Kontrolle über die abgefragte Subgraphenversion besteht. Dies hat jedoch zur Folge, dass der Abfragecode jedes Mal manuell aktualisiert werden muss, wenn eine neue Version des Subgraphen veröffentlicht wird.
 
diff --git a/website/src/pages/en/indexing/new-chain-integration.mdx b/website/src/pages/en/indexing/new-chain-integration.mdx
index a52a1463ab6c..49cd840a9c99 100644
--- a/website/src/pages/en/indexing/new-chain-integration.mdx
+++ b/website/src/pages/en/indexing/new-chain-integration.mdx
@@ -62,7 +62,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 
diff --git a/website/src/pages/en/indexing/overview.mdx b/website/src/pages/en/indexing/overview.mdx
index dcd86518cfe2..73d230f58b5a 100644
--- a/website/src/pages/en/indexing/overview.mdx
+++ b/website/src/pages/en/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/en/indexing/tooling/graph-node.mdx b/website/src/pages/en/indexing/tooling/graph-node.mdx
index 1cabbefa3f28..21a5eff49e64 100644
--- a/website/src/pages/en/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/en/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### IPFS Nodes
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Prometheus metrics server
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Getting started with Kubernetes
diff --git a/website/src/pages/en/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/en/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index f894f3d37dc2..acb211f2c9f1 100644
--- a/website/src/pages/en/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/en/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/en/subgraphs/guides/near.mdx b/website/src/pages/en/subgraphs/guides/near.mdx
index e78a69eb7fa2..34adc65f9175 100644
--- a/website/src/pages/en/subgraphs/guides/near.mdx
+++ b/website/src/pages/en/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/en/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/en/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 59d5d230449e..c48a3021233a 100644
--- a/website/src/pages/en/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/en/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -14,7 +14,7 @@ Both identifiers are accessible in [Subgraph Studio](https://thegraph.com/studio
 
 ## Deployment ID
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/es/indexing/new-chain-integration.mdx b/website/src/pages/es/indexing/new-chain-integration.mdx
index 5e56afca4d75..aa3ef7b91fae 100644
--- a/website/src/pages/es/indexing/new-chain-integration.mdx
+++ b/website/src/pages/es/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 
diff --git a/website/src/pages/es/indexing/overview.mdx b/website/src/pages/es/indexing/overview.mdx
index cf592d9ad7e4..1eacc8b17e82 100644
--- a/website/src/pages/es/indexing/overview.mdx
+++ b/website/src/pages/es/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/es/indexing/tooling/graph-node.mdx b/website/src/pages/es/indexing/tooling/graph-node.mdx
index 4563bd8444bb..a4d3e89088be 100644
--- a/website/src/pages/es/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/es/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### Nodos IPFS
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Servidor de métricas Prometheus
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Introducción a Kubernetes
diff --git a/website/src/pages/es/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/es/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 67c076d0a156..ac0a6b970883 100644
--- a/website/src/pages/es/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/es/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/es/subgraphs/guides/near.mdx b/website/src/pages/es/subgraphs/guides/near.mdx
index f22a497db7e1..29c6ae49614c 100644
--- a/website/src/pages/es/subgraphs/guides/near.mdx
+++ b/website/src/pages/es/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/es/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/es/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 17258dd13ea1..3b55aea5b072 100644
--- a/website/src/pages/es/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/es/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## Deployment ID
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/fr/indexing/new-chain-integration.mdx b/website/src/pages/fr/indexing/new-chain-integration.mdx
index ab70ce6efb3a..68451eafa01f 100644
--- a/website/src/pages/fr/indexing/new-chain-integration.mdx
+++ b/website/src/pages/fr/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Ne changez pas le nom de la var env elle-même. Il doit rester `ethereum`  même si le nom du réseau est différent.
 
-3. Exécutez un nœud IPFS ou utilisez celui utilisé par The Graph : https://api.thegraph.com/ipfs/
+3. Exécutez un nœud IPFS ou utilisez celui utilisé par The Graph : https://ipfs.thegraph.com
 
 ## Subgraphs alimentés par des substreams
 
diff --git a/website/src/pages/fr/indexing/overview.mdx b/website/src/pages/fr/indexing/overview.mdx
index 1c0d0f9c7221..b95a482012b1 100644
--- a/website/src/pages/fr/indexing/overview.mdx
+++ b/website/src/pages/fr/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Service de l'Indexeur** - Gère toutes les communications externes requises avec le réseau. Il partage les modèles de coûts et les états d'indexation, transmet les requêtes des passerelles à un Graph Node et gère les paiements des requêtes via des canaux d'état avec la passerelle.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Commencer à utiliser Docker
diff --git a/website/src/pages/fr/indexing/tooling/graph-node.mdx b/website/src/pages/fr/indexing/tooling/graph-node.mdx
index ea35e2fb9680..223e51b5cb7e 100644
--- a/website/src/pages/fr/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/fr/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### Nœuds IPFS
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Serveur de métriques Prometheus
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Bien démarrer avec Kubernetes
diff --git a/website/src/pages/fr/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/fr/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 88b91fcd179c..aa630f888430 100644
--- a/website/src/pages/fr/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/fr/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ UTILISATION
 
 FLAGS
   -h, --help                   Affiche l'aide CLI.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Charge les résultats du build sur un noeud IPFS.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Charge les résultats du build sur un noeud IPFS.
   --ipfs-hash=<value>          hash IPFS du manifeste du subgraph à déployer.
   --protocol-network=<option>  [default: arbitrum-one] Le réseau à utiliser pour le déploiement du subgraph.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/fr/subgraphs/guides/near.mdx b/website/src/pages/fr/subgraphs/guides/near.mdx
index 71baadc8ba82..2cdbc800e5f3 100644
--- a/website/src/pages/fr/subgraphs/guides/near.mdx
+++ b/website/src/pages/fr/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Une fois votre subgraph créé, vous pouvez le déployer en utilisant la command
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # crée un subgrpah sur un Graph Node local (sur Subgraph Studio, cela se fait via l'interface utilisateur)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # upload les fichiers de build vers un endpoint IPFS spécifié, puis déploie le subgraph vers un Graph Node spécifié sur la base du hash IPFS du manifeste
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # upload les fichiers de build vers un endpoint IPFS spécifié, puis déploie le subgraph vers un Graph Node spécifié sur la base du hash IPFS du manifeste
 ```
 
 La configuration des nœuds dépend de l'endroit où le subgraph est déployé.
diff --git a/website/src/pages/fr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/fr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index acd40aface24..603882975c27 100644
--- a/website/src/pages/fr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/fr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Voici les principales différences entre les deux ID : ![](/img/subgraph-id-vs-d
 
 ## Identifiant de déploiement
 
-L'ID de déploiement est le hash IPFS du fichier manifeste compilé, qui fait référence à d'autres fichiers sur IPFS au lieu d'URL relatives sur l'ordinateur. Par exemple, le manifeste compilé est accessible via : `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. Pour modifier l'ID de déploiement, il suffit de mettre à jour le fichier de manifeste, en modifiant par exemple le champ de description comme décrit dans la [documentation du manifeste du subgraph](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+L'ID de déploiement est le hash IPFS du fichier manifeste compilé, qui fait référence à d'autres fichiers sur IPFS au lieu d'URL relatives sur l'ordinateur. Par exemple, le manifeste compilé est accessible via : `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. Pour modifier l'ID de déploiement, il suffit de mettre à jour le fichier de manifeste, en modifiant par exemple le champ de description comme décrit dans la [documentation du manifeste du subgraph](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 Lorsque des requêtes sont effectuées à l'aide de l'ID de déploiement d'un subgraph, nous spécifions une version de ce subgraph à interroger. L'utilisation de l'ID de déploiement pour interroger une version spécifique du subgraph donne lieu à une configuration plus sophistiquée et plus robuste, car il y a un contrôle total sur la version du subgraph interrogée. Toutefois, cela implique la nécessité de mettre à jour manuellement le code d'interrogation chaque fois qu'une nouvelle version du subgraph est publiée.
 
diff --git a/website/src/pages/hi/indexing/new-chain-integration.mdx b/website/src/pages/hi/indexing/new-chain-integration.mdx
index 1863ea5fa2bc..b58aef74ed53 100644
--- a/website/src/pages/hi/indexing/new-chain-integration.mdx
+++ b/website/src/pages/hi/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ JSON-RPC और Firehose दोनों ही सबग्राफ के ल
 
    > कृपया पर्यावरण चर ethereum को खुद नाम में बदलें नहीं। यही रहना चाहिए, चाहे network का नाम भिन्न हो।
 
-3. एक IPFS node चलाएं या उसे The Graph द्वारा उपयोग किया जाने वाले node का उपयोग करें: https://api.thegraph.com/ipfs/
+3. एक IPFS node चलाएं या उसे The Graph द्वारा उपयोग किया जाने वाले node का उपयोग करें: https://ipfs.thegraph.com
 
 ## सबस्ट्रीम-संचालित सबग्राफ की सेवा
 
diff --git a/website/src/pages/hi/indexing/overview.mdx b/website/src/pages/hi/indexing/overview.mdx
index 38a778b97854..4a9a5d556a9a 100644
--- a/website/src/pages/hi/indexing/overview.mdx
+++ b/website/src/pages/hi/indexing/overview.mdx
@@ -131,7 +131,7 @@ Indexer के इंफ्रास्ट्रक्चर के केंद
 
 - **डेटा एंडपॉइंट** - EVM-संगत नेटवर्क्स के लिए, Graph Node को एक ऐसे एंडपॉइंट से कनेक्ट करने की आवश्यकता होती है जो EVM-संगत JSON-RPC API को एक्सपोज़ करता हो। यह एक सिंगल क्लाइंट के रूप में हो सकता है या यह एक अधिक जटिल सेटअप हो सकता है जो मल्टीपल क्लाइंट्स के बीच लोड बैलेंस करता हो। यह जानना महत्वपूर्ण है कि कुछ सबग्राफ को विशेष क्लाइंट क्षमताओं की आवश्यकता हो सकती है, जैसे कि आर्काइव मोड और/या पैरिटी ट्रेसिंग API।
 
-- **IPFS node (संस्करण 5 से कम)** - सबग्राफ डिप्लॉयमेंट मेटाडेटा IPFS नेटवर्क पर स्टोर किया जाता है। The Graph Node मुख्य रूप से सबग्राफ डिप्लॉयमेंट के दौरान IPFS node तक पहुंचता है ताकि सबग्राफ मैनिफेस्ट और सभी लिंक की गई फ़ाइलों को प्राप्त किया जा सके। नेटवर्क Indexers को अपना स्वयं का IPFS node होस्ट करने की आवश्यकता नहीं है, नेटवर्क के लिए एक IPFS node होस्ट किया गया है: https://ipfs.network.thegraph.com.
+- **IPFS node (संस्करण 5 से कम)** - सबग्राफ डिप्लॉयमेंट मेटाडेटा IPFS नेटवर्क पर स्टोर किया जाता है। The Graph Node मुख्य रूप से सबग्राफ डिप्लॉयमेंट के दौरान IPFS node तक पहुंचता है ताकि सबग्राफ मैनिफेस्ट और सभी लिंक की गई फ़ाइलों को प्राप्त किया जा सके। नेटवर्क Indexers को अपना स्वयं का IPFS node होस्ट करने की आवश्यकता नहीं है, नेटवर्क के लिए एक IPFS node होस्ट किया गया है: https://ipfs.thegraph.com.
 
 - **Indexer सेवा** - आवश्यक बाहरी संचार को नेटवर्क के साथ संभालती है। लागत मॉडल और इंडेक्सिंग स्थितियों को साझा करती है, गेटवे से आने वाले क्वेरी अनुरोधों को एक Graph Node तक पहुंचाती है, और गेटवे के साथ स्टेट चैनलों के माध्यम से क्वेरी भुगतान को प्रबंधित करती है।
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Docker का उपयोग शुरू करना
diff --git a/website/src/pages/hi/indexing/tooling/graph-node.mdx b/website/src/pages/hi/indexing/tooling/graph-node.mdx
index fad29c77e35e..08ef77f1e87c 100644
--- a/website/src/pages/hi/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/hi/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ Graph Node (और पूरा indexer stack) को bare metal पर या 
 
 ### आईपीएफएस नोड्स
 
-सबग्राफ तैनाती मेटाडेटा IPFS नेटवर्क पर संग्रहीत होता है। ग्राफ नोड मुख्य रूप से सबग्राफ तैनाती के दौरान IPFS नोड तक पहुँचता है ताकि सबग्राफ मैनिफेस्ट और सभी लिंक किए गए फ़ाइलों को प्राप्त कर सके। नेटवर्क Indexer को अपने स्वयं के IPFS नोड की मेज़बानी करने की आवश्यकता नहीं है। नेटवर्क के लिए एक IPFS नोड यहाँ होस्ट किया गया है: https://ipfs.network.thegraph.com.
+सबग्राफ तैनाती मेटाडेटा IPFS नेटवर्क पर संग्रहीत होता है। ग्राफ नोड मुख्य रूप से सबग्राफ तैनाती के दौरान IPFS नोड तक पहुँचता है ताकि सबग्राफ मैनिफेस्ट और सभी लिंक किए गए फ़ाइलों को प्राप्त कर सके। नेटवर्क Indexer को अपने स्वयं के IPFS नोड की मेज़बानी करने की आवश्यकता नहीं है। नेटवर्क के लिए एक IPFS नोड यहाँ होस्ट किया गया है: https://ipfs.thegraph.com.
 
 ### प्रोमेथियस मेट्रिक्स सर्वर
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Kubernetes के साथ शुरुआत करना
diff --git a/website/src/pages/hi/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/hi/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 4de4472caf4c..ef1a8060175f 100644
--- a/website/src/pages/hi/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/hi/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/hi/subgraphs/guides/near.mdx b/website/src/pages/hi/subgraphs/guides/near.mdx
index d8b019189a96..4c047b90e782 100644
--- a/website/src/pages/hi/subgraphs/guides/near.mdx
+++ b/website/src/pages/hi/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ More information on सबग्राफ Studio पर सबग्राफ 
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # एक स्थानीय ग्राफ-नोड पर सबग्राफ बनाता है (सबग्राफ Studio पर, यह UI के माध्यम से किया जाता है)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # निर्मित फ़ाइलों को निर्दिष्ट IPFS endpoint पर अपलोड करता है, और फिर manifest IPFS hash के आधार पर निर्दिष्ट ग्राफ-नोड पर सबग्राफ को डिप्लॉय करता है
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # निर्मित फ़ाइलों को निर्दिष्ट IPFS endpoint पर अपलोड करता है, और फिर manifest IPFS hash के आधार पर निर्दिष्ट ग्राफ-नोड पर सबग्राफ को डिप्लॉय करता है
 ```
 
 नोड कॉन्फ़िगरेशन इस बात पर निर्भर करेगा कि सबग्राफ कहाँ तैनात किया जा रहा है।
diff --git a/website/src/pages/hi/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/hi/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 17258dd13ea1..3b55aea5b072 100644
--- a/website/src/pages/hi/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/hi/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## Deployment ID
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/it/indexing/new-chain-integration.mdx b/website/src/pages/it/indexing/new-chain-integration.mdx
index 670e06c752c3..d6815b2b832b 100644
--- a/website/src/pages/it/indexing/new-chain-integration.mdx
+++ b/website/src/pages/it/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 
diff --git a/website/src/pages/it/indexing/overview.mdx b/website/src/pages/it/indexing/overview.mdx
index 371d0f48cf9a..6f8dcb45fe8f 100644
--- a/website/src/pages/it/indexing/overview.mdx
+++ b/website/src/pages/it/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/it/indexing/tooling/graph-node.mdx b/website/src/pages/it/indexing/tooling/graph-node.mdx
index 32015adbd8fd..0c377f1ec50a 100644
--- a/website/src/pages/it/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/it/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### Nodi IPFS
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Server di metriche Prometheus
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Come iniziare con Kubernetes
diff --git a/website/src/pages/it/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/it/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 1672a6619d13..985a5bd7d9d7 100644
--- a/website/src/pages/it/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/it/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/it/subgraphs/guides/near.mdx b/website/src/pages/it/subgraphs/guides/near.mdx
index baa5bcc79157..f3d88823e92e 100644
--- a/website/src/pages/it/subgraphs/guides/near.mdx
+++ b/website/src/pages/it/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/it/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/it/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 17258dd13ea1..3b55aea5b072 100644
--- a/website/src/pages/it/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/it/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## Deployment ID
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/ja/indexing/new-chain-integration.mdx b/website/src/pages/ja/indexing/new-chain-integration.mdx
index f6fa2b643fc3..ae167dd08eef 100644
--- a/website/src/pages/ja/indexing/new-chain-integration.mdx
+++ b/website/src/pages/ja/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 
diff --git a/website/src/pages/ja/indexing/overview.mdx b/website/src/pages/ja/indexing/overview.mdx
index 25b94c36ca88..4478e166a307 100644
--- a/website/src/pages/ja/indexing/overview.mdx
+++ b/website/src/pages/ja/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/ja/indexing/tooling/graph-node.mdx b/website/src/pages/ja/indexing/tooling/graph-node.mdx
index dfbb9aeea657..82e3a193eb7a 100644
--- a/website/src/pages/ja/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/ja/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### IPFSノード
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Prometheus メトリクスサーバー
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Kubernetesを始めるにあたって
diff --git a/website/src/pages/ja/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/ja/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index c26672ec6b84..4efa2628552b 100644
--- a/website/src/pages/ja/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/ja/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/ja/subgraphs/guides/near.mdx b/website/src/pages/ja/subgraphs/guides/near.mdx
index 9e3738689919..8eb27cab1c50 100644
--- a/website/src/pages/ja/subgraphs/guides/near.mdx
+++ b/website/src/pages/ja/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/ja/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/ja/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 4bf98ccc0c6f..2bea8b063f04 100644
--- a/website/src/pages/ja/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/ja/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## Deployment ID
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/ko/indexing/new-chain-integration.mdx b/website/src/pages/ko/indexing/new-chain-integration.mdx
index 670e06c752c3..d6815b2b832b 100644
--- a/website/src/pages/ko/indexing/new-chain-integration.mdx
+++ b/website/src/pages/ko/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 
diff --git a/website/src/pages/ko/indexing/overview.mdx b/website/src/pages/ko/indexing/overview.mdx
index 4a980db27f12..fa6c22b77a86 100644
--- a/website/src/pages/ko/indexing/overview.mdx
+++ b/website/src/pages/ko/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/ko/indexing/tooling/graph-node.mdx b/website/src/pages/ko/indexing/tooling/graph-node.mdx
index edde8a157fd3..b535d6a471e7 100644
--- a/website/src/pages/ko/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/ko/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### IPFS Nodes
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Prometheus metrics server
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Getting started with Kubernetes
diff --git a/website/src/pages/ko/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/ko/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 2bc0ec5f514c..e3e3a7e3d455 100644
--- a/website/src/pages/ko/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/ko/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/ko/subgraphs/guides/near.mdx b/website/src/pages/ko/subgraphs/guides/near.mdx
index e78a69eb7fa2..34adc65f9175 100644
--- a/website/src/pages/ko/subgraphs/guides/near.mdx
+++ b/website/src/pages/ko/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/ko/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/ko/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 17258dd13ea1..3b55aea5b072 100644
--- a/website/src/pages/ko/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/ko/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## Deployment ID
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/mr/indexing/new-chain-integration.mdx b/website/src/pages/mr/indexing/new-chain-integration.mdx
index 670e06c752c3..d6815b2b832b 100644
--- a/website/src/pages/mr/indexing/new-chain-integration.mdx
+++ b/website/src/pages/mr/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 
diff --git a/website/src/pages/mr/indexing/overview.mdx b/website/src/pages/mr/indexing/overview.mdx
index 9d78f7612f01..a7a768afd00b 100644
--- a/website/src/pages/mr/indexing/overview.mdx
+++ b/website/src/pages/mr/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/mr/indexing/tooling/graph-node.mdx b/website/src/pages/mr/indexing/tooling/graph-node.mdx
index 687f1ea42338..66e05f181528 100644
--- a/website/src/pages/mr/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/mr/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### आयपीएफएस नोड्स
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### प्रोमिथियस मेट्रिक्स सर्व्हर
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Kubernetes सह प्रारंभ करणे
diff --git a/website/src/pages/mr/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/mr/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 78b641e5ae0a..5c0177c85d87 100644
--- a/website/src/pages/mr/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/mr/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/mr/subgraphs/guides/near.mdx b/website/src/pages/mr/subgraphs/guides/near.mdx
index 4a183fca2e16..9f60b0c9dfe6 100644
--- a/website/src/pages/mr/subgraphs/guides/near.mdx
+++ b/website/src/pages/mr/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/mr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/mr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 17258dd13ea1..3b55aea5b072 100644
--- a/website/src/pages/mr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/mr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## Deployment ID
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/nl/indexing/new-chain-integration.mdx b/website/src/pages/nl/indexing/new-chain-integration.mdx
index 670e06c752c3..d6815b2b832b 100644
--- a/website/src/pages/nl/indexing/new-chain-integration.mdx
+++ b/website/src/pages/nl/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 
diff --git a/website/src/pages/nl/indexing/overview.mdx b/website/src/pages/nl/indexing/overview.mdx
index 89c13c8ab279..8a9a992079b5 100644
--- a/website/src/pages/nl/indexing/overview.mdx
+++ b/website/src/pages/nl/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/nl/indexing/tooling/graph-node.mdx b/website/src/pages/nl/indexing/tooling/graph-node.mdx
index edde8a157fd3..b535d6a471e7 100644
--- a/website/src/pages/nl/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/nl/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### IPFS Nodes
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Prometheus metrics server
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Getting started with Kubernetes
diff --git a/website/src/pages/nl/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/nl/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 2bc0ec5f514c..e3e3a7e3d455 100644
--- a/website/src/pages/nl/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/nl/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/nl/subgraphs/guides/near.mdx b/website/src/pages/nl/subgraphs/guides/near.mdx
index e78a69eb7fa2..34adc65f9175 100644
--- a/website/src/pages/nl/subgraphs/guides/near.mdx
+++ b/website/src/pages/nl/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/nl/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/nl/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 17258dd13ea1..3b55aea5b072 100644
--- a/website/src/pages/nl/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/nl/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## Deployment ID
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/pl/indexing/new-chain-integration.mdx b/website/src/pages/pl/indexing/new-chain-integration.mdx
index 670e06c752c3..d6815b2b832b 100644
--- a/website/src/pages/pl/indexing/new-chain-integration.mdx
+++ b/website/src/pages/pl/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 
diff --git a/website/src/pages/pl/indexing/overview.mdx b/website/src/pages/pl/indexing/overview.mdx
index 4a980db27f12..fa6c22b77a86 100644
--- a/website/src/pages/pl/indexing/overview.mdx
+++ b/website/src/pages/pl/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/pl/indexing/tooling/graph-node.mdx b/website/src/pages/pl/indexing/tooling/graph-node.mdx
index edde8a157fd3..b535d6a471e7 100644
--- a/website/src/pages/pl/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/pl/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### IPFS Nodes
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Prometheus metrics server
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Getting started with Kubernetes
diff --git a/website/src/pages/pl/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/pl/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 2bc0ec5f514c..e3e3a7e3d455 100644
--- a/website/src/pages/pl/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/pl/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/pl/subgraphs/guides/near.mdx b/website/src/pages/pl/subgraphs/guides/near.mdx
index e78a69eb7fa2..34adc65f9175 100644
--- a/website/src/pages/pl/subgraphs/guides/near.mdx
+++ b/website/src/pages/pl/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/pl/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/pl/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 17258dd13ea1..3b55aea5b072 100644
--- a/website/src/pages/pl/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/pl/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## Deployment ID
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/pt/indexing/new-chain-integration.mdx b/website/src/pages/pt/indexing/new-chain-integration.mdx
index bcaf712fb2cb..066338a80a92 100644
--- a/website/src/pages/pt/indexing/new-chain-integration.mdx
+++ b/website/src/pages/pt/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configurar um Graph Node é tão fácil quanto preparar o seu ambiente local. Qu
 
    > Não mude o nome do env var. Ele deve permanecer como `ethereum` mesmo se o nome da rede for diferente.
 
-3. Execute um node IPFS ou use aquele usado pelo The Graph: https://api.thegraph.com/ipfs/
+3. Execute um node IPFS ou use aquele usado pelo The Graph: https://ipfs.thegraph.com
 
 ## Subgraphs movidos por Substreams
 
diff --git a/website/src/pages/pt/indexing/overview.mdx b/website/src/pages/pt/indexing/overview.mdx
index 02343b809f03..db2298351ab2 100644
--- a/website/src/pages/pt/indexing/overview.mdx
+++ b/website/src/pages/pt/indexing/overview.mdx
@@ -131,7 +131,7 @@ O núcleo da infraestrutura de um Indexador é o Graph Node, que monitora as red
 
 - **Endpoint de dados** — Para redes compatíveis com EVMs, o Graph Node deve estar conectado a um endpoint que expõe uma API JSON-RPC compatível com EVMs. Isto pode ser um único cliente, ou um setup mais complexo que carrega saldos em várias redes. É importante saber que certos subgraphs exigirão capabilidades particulares de clientes, como um modo de arquivo e/ou uma API de rastreamento.
 
-- **Node IPFS (versão abaixo de 5)** — Os metadados de lançamento de subgraph são armazenados na rede IPFS. O Graph Node acessa primariamente o node IPFS durante o lançamento do subgraph, para retirar o manifest e todos os arquivos ligados. Indexadores de rede não precisam hospedar seu próprio node IPFS, pois já há um hospedado para a rede em https://ipfs.network.thegraph.com.
+- **Node IPFS (versão abaixo de 5)** — Os metadados de lançamento de subgraph são armazenados na rede IPFS. O Graph Node acessa primariamente o node IPFS durante o lançamento do subgraph, para retirar o manifest e todos os arquivos ligados. Indexadores de rede não precisam hospedar seu próprio node IPFS, pois já há um hospedado para a rede em https://ipfs.thegraph.com.
 
 - **Serviço de Indexador** — Cuida de todas as comunicações externas com a rede requeridas. Divide modelos de custo e estados de indexação, passa pedidos de query de gateways para um Graph Node, e monitora os pagamentos de query através de canais de estado com o gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Como começar a usar o Docker
diff --git a/website/src/pages/pt/indexing/tooling/graph-node.mdx b/website/src/pages/pt/indexing/tooling/graph-node.mdx
index 3d8d68eca293..56d3d776497e 100644
--- a/website/src/pages/pt/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/pt/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ Enquanto alguns subgraphs exigem apenas um node completo, alguns podem ter recur
 
 ### Nodes IPFS
 
-Os metadados de implantação de subgraph são armazenados na rede IPFS. O Graph Node acessa primariamente o node IPFS durante a implantação do subgraph, para retirar o manifest e todos os arquivos ligados. Os indexadores de rede não precisam hospedar seu próprio node IPFS. Um node IPFS para a rede é hospedado em https://ipfs.network.thegraph.com.
+Os metadados de implantação de subgraph são armazenados na rede IPFS. O Graph Node acessa primariamente o node IPFS durante a implantação do subgraph, para retirar o manifest e todos os arquivos ligados. Os indexadores de rede não precisam hospedar seu próprio node IPFS. Um node IPFS para a rede é hospedado em https://ipfs.thegraph.com.
 
 ### Servidor de métricas Prometheus
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Como começar com Kubernetes
diff --git a/website/src/pages/pt/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/pt/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 1d25ded18a61..9347c3078856 100644
--- a/website/src/pages/pt/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/pt/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Mostra ajuda da CLI.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Envia resultados da build a um node IPFS.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Envia resultados da build a um node IPFS.
   --ipfs-hash=<value>          Hash IPFS do manifest do subgraph a ser implantado.
   --protocol-network=<option>  [default: arbitrum-one] A rede a ser usada para a implantação do subgraph.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/pt/subgraphs/guides/near.mdx b/website/src/pages/pt/subgraphs/guides/near.mdx
index db728bc51e51..d4e3e1953b72 100644
--- a/website/src/pages/pt/subgraphs/guides/near.mdx
+++ b/website/src/pages/pt/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Quando o seu subgraph estiver pronto, implante o seu subgraph com o comando de C
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # cria um subgraph num Graph Node local (no Subgraph Studio, isto é feito via a interface)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # envia os arquivos do build a um ponto final IPFS especificado, e implanta o subgraph num Graph Node com base no hash IPFS do manifest
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # envia os arquivos do build a um ponto final IPFS especificado, e implanta o subgraph num Graph Node com base no hash IPFS do manifest
 ```
 
 A configuração do nódulo dependerá de onde o subgraph será implantado.
diff --git a/website/src/pages/pt/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/pt/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index a9cef21ce27f..d955d26ca793 100644
--- a/website/src/pages/pt/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/pt/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Aqui estão algumas diferenças importantes entre as duas IDs: ![](/img/subgraph
 
 ## ID de Lançamento
 
-A ID de Implantação é o hash IPFS do arquivo manifest compilado, que refere a outros arquivos no IPFS em vez de URLs relativas no computador. Por exemplo, o manifest compilado pode ser acessado via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. Para mudar a ID de Implantação, basta atualizar o arquivo manifest, por ex., modificar o arquivo de descrição como descrito na [documentação do manifest de subgraph](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+A ID de Implantação é o hash IPFS do arquivo manifest compilado, que refere a outros arquivos no IPFS em vez de URLs relativas no computador. Por exemplo, o manifest compilado pode ser acessado via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. Para mudar a ID de Implantação, basta atualizar o arquivo manifest, por ex., modificar o arquivo de descrição como descrito na [documentação do manifest de subgraph](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 Quando queries são feitas com a ID de Implantação de um subgraph, especificamos uma versão daquele subgraph para buscar. Usar a ID de Implantação para consultar uma versão específica de subgraph resulta em um setup mais sofisticado e robusto, já que há controle total sobre a versão do subgraph a ser consultada. Porém, isto resulta na necessidade de atualizar o código de queries manualmente toda vez que uma nova versão do subgraph é editada.
 
diff --git a/website/src/pages/ro/indexing/new-chain-integration.mdx b/website/src/pages/ro/indexing/new-chain-integration.mdx
index 670e06c752c3..d6815b2b832b 100644
--- a/website/src/pages/ro/indexing/new-chain-integration.mdx
+++ b/website/src/pages/ro/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 
diff --git a/website/src/pages/ro/indexing/overview.mdx b/website/src/pages/ro/indexing/overview.mdx
index 4a980db27f12..fa6c22b77a86 100644
--- a/website/src/pages/ro/indexing/overview.mdx
+++ b/website/src/pages/ro/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/ro/indexing/tooling/graph-node.mdx b/website/src/pages/ro/indexing/tooling/graph-node.mdx
index edde8a157fd3..b535d6a471e7 100644
--- a/website/src/pages/ro/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/ro/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### IPFS Nodes
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Prometheus metrics server
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Getting started with Kubernetes
diff --git a/website/src/pages/ro/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/ro/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 2bc0ec5f514c..e3e3a7e3d455 100644
--- a/website/src/pages/ro/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/ro/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/ro/subgraphs/guides/near.mdx b/website/src/pages/ro/subgraphs/guides/near.mdx
index e78a69eb7fa2..34adc65f9175 100644
--- a/website/src/pages/ro/subgraphs/guides/near.mdx
+++ b/website/src/pages/ro/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/ro/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/ro/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 17258dd13ea1..3b55aea5b072 100644
--- a/website/src/pages/ro/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/ro/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## Deployment ID
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/ru/indexing/new-chain-integration.mdx b/website/src/pages/ru/indexing/new-chain-integration.mdx
index 8b23af33ebd1..9fafd5dbd230 100644
--- a/website/src/pages/ru/indexing/new-chain-integration.mdx
+++ b/website/src/pages/ru/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Не меняйте само имя переменной env. Оно должно оставаться `ethereum`, даже если имя сети отличается.
 
-3. Запустите ноду IPFS или используйте ту, которая используется The Graph: https://api.thegraph.com/ipfs/
+3. Запустите ноду IPFS или используйте ту, которая используется The Graph: https://ipfs.thegraph.com
 
 ## Субграфы, работающие на основе субпотоков (Substreams)
 
diff --git a/website/src/pages/ru/indexing/overview.mdx b/website/src/pages/ru/indexing/overview.mdx
index 30c9ec939dcd..50c03111ca99 100644
--- a/website/src/pages/ru/indexing/overview.mdx
+++ b/website/src/pages/ru/indexing/overview.mdx
@@ -131,7 +131,7 @@ query indexerAllocations {
 
 - **Конечная точка данных** – для сетей, совместимых с EVM, Graph Node должна быть подключена к конечной точке, предоставляющей JSON-RPC API, совместимый с EVM. Это может быть как один клиент, так и более сложная конфигурация с балансировкой нагрузки между несколькими клиентами. Важно учитывать, что некоторые Субграфы требуют определённых возможностей клиента, таких как архивный режим и/или API трассировки Parity.
 
-- **IPFS-нода (версия ниже 5)** – метаданные развертывания Субграфа хранятся в сети IPFS. Graph Node в основном обращается к IPFS-ноде во время развертывания Субграфа, чтобы получить манифест Субграфа и все связанные файлы. Индексаторы сети не обязаны размещать свою собственную IPFS-ноду, так как для сети уже развернута IPFS-нода по адресу: [https://ipfs.network.thegraph.com](https://ipfs.network.thegraph.com).
+- **IPFS-нода (версия ниже 5)** – метаданные развертывания Субграфа хранятся в сети IPFS. Graph Node в основном обращается к IPFS-ноде во время развертывания Субграфа, чтобы получить манифест Субграфа и все связанные файлы. Индексаторы сети не обязаны размещать свою собственную IPFS-ноду, так как для сети уже развернута IPFS-нода по адресу: [https://ipfs.thegraph.com](https://ipfs.thegraph.com).
 
 - **Сервис Индексатора** – обрабатывает все необходимые внешние коммуникации с сетью. Делится моделями стоимости и статусами индексирования, передаёт запросы от шлюзов в Graph Node и управляет платежами за запросы через каналы состояния со шлюзом.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Начало работы с Docker
diff --git a/website/src/pages/ru/indexing/tooling/graph-node.mdx b/website/src/pages/ru/indexing/tooling/graph-node.mdx
index 27f730d64966..b33ca1b3709a 100644
--- a/website/src/pages/ru/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/ru/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### Ноды IPFS
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Сервер метрик Prometheus
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Начало работы с Kubernetes
diff --git a/website/src/pages/ru/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/ru/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 8838c90b6889..e207c46cc418 100644
--- a/website/src/pages/ru/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/ru/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/ru/subgraphs/guides/near.mdx b/website/src/pages/ru/subgraphs/guides/near.mdx
index a71aee9acdca..a62bb96e7932 100644
--- a/website/src/pages/ru/subgraphs/guides/near.mdx
+++ b/website/src/pages/ru/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Subgraph Studio и Индексатор обновлений в The Graph Networ
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # создает субграф на локальной Graph Node (в Subgraph Studio это делается через UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # загружает файлы сборки на указанную конечную точку IPFS и затем развертывает субграф на указанном Graph Node, основываясь на IPFS-хэше манифеста
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # загружает файлы сборки на указанную конечную точку IPFS и затем развертывает субграф на указанном Graph Node, основываясь на IPFS-хэше манифеста
 ```
 
 Конфигурация ноды будет зависеть от того, где развертывается субграф.
diff --git a/website/src/pages/ru/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/ru/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index b697d9cfd5e6..a2de9e8940cb 100644
--- a/website/src/pages/ru/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/ru/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ title: Идентификатор субграфа vs Идентификатор
 
 ## Идентификатор развертывания
 
-Идентификатор развертывания — это IPFS-хеш скомпилированного файла манифеста, который ссылается на другие файлы в IPFS вместо относительных URL на компьютере. Например, скомпилированный манифест можно открыть по ссылке: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. Чтобы изменить идентификатор развертывания, можно просто обновить файл манифеста, например, изменив поле description, как описано в [документации манифеста субграфа](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+Идентификатор развертывания — это IPFS-хеш скомпилированного файла манифеста, который ссылается на другие файлы в IPFS вместо относительных URL на компьютере. Например, скомпилированный манифест можно открыть по ссылке: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. Чтобы изменить идентификатор развертывания, можно просто обновить файл манифеста, например, изменив поле description, как описано в [документации манифеста субграфа](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 Когда запросы выполняются с использованием идентификатора развертывания субграфа, мы указываем конкретную версию этого субграфа для запроса. Использование идентификатора развертывания для запроса определённой версии субграфа обеспечивает более продвинутую и надежную настройку, так как даёт полный контроль над версией субграфа, к которой выполняется запрос. Однако это приводит к необходимости вручную обновлять код запроса каждый раз при публикации новой версии субграфа.
 
diff --git a/website/src/pages/sv/indexing/new-chain-integration.mdx b/website/src/pages/sv/indexing/new-chain-integration.mdx
index d8cb301e3902..746a7b159356 100644
--- a/website/src/pages/sv/indexing/new-chain-integration.mdx
+++ b/website/src/pages/sv/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 
diff --git a/website/src/pages/sv/indexing/overview.mdx b/website/src/pages/sv/indexing/overview.mdx
index b355374c5949..c265f0efff66 100644
--- a/website/src/pages/sv/indexing/overview.mdx
+++ b/website/src/pages/sv/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/sv/indexing/tooling/graph-node.mdx b/website/src/pages/sv/indexing/tooling/graph-node.mdx
index e3d030167389..73dd33271ffe 100644
--- a/website/src/pages/sv/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/sv/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### IPFS-noder
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Prometheus server för mätvärden
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Komma igång med Kubernetes
diff --git a/website/src/pages/sv/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/sv/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index e13f4a7f9f7c..905759049aca 100644
--- a/website/src/pages/sv/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/sv/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/sv/subgraphs/guides/near.mdx b/website/src/pages/sv/subgraphs/guides/near.mdx
index d766a44ad511..15ad1537fda2 100644
--- a/website/src/pages/sv/subgraphs/guides/near.mdx
+++ b/website/src/pages/sv/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/sv/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/sv/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 17258dd13ea1..3b55aea5b072 100644
--- a/website/src/pages/sv/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/sv/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## Deployment ID
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/tr/indexing/new-chain-integration.mdx b/website/src/pages/tr/indexing/new-chain-integration.mdx
index 07e538ae9bae..65b625586008 100644
--- a/website/src/pages/tr/indexing/new-chain-integration.mdx
+++ b/website/src/pages/tr/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Çevre değişkeni adının kendisini değiştirmeyin. Ağ adı farklı olsa bile `ethereum` olarak kalmalıdır.
 
-3. Bir IPFS düğümü çalıştırın veya The Graph tarafından kullanılanı kullanın: https://api.thegraph.com/ipfs/
+3. Bir IPFS düğümü çalıştırın veya The Graph tarafından kullanılanı kullanın: https://ipfs.thegraph.com
 
 ## Substreams destekli Subgraph'ler
 
diff --git a/website/src/pages/tr/indexing/overview.mdx b/website/src/pages/tr/indexing/overview.mdx
index 6a9d93397c39..6017f2fdc09e 100644
--- a/website/src/pages/tr/indexing/overview.mdx
+++ b/website/src/pages/tr/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/tr/indexing/tooling/graph-node.mdx b/website/src/pages/tr/indexing/tooling/graph-node.mdx
index 5f8d0267d3e0..f9ea58a60ed4 100644
--- a/website/src/pages/tr/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/tr/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### IPFS Düğümleri
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Prometheus metrik sunucusu
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Kubernetes'i kullanmaya başlarken
diff --git a/website/src/pages/tr/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/tr/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index e315eb8c74fb..2cc351b3d7b1 100644
--- a/website/src/pages/tr/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/tr/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ KULLANIM
 
 BAYRAKLAR
   -h, --help                   CLI yardımını gösterir.
-  -i, --ipfs=<value>           [varsayılan: https://api.thegraph.com/ipfs/api/v0] Derleme sonuçlarını bir IPFS düğümüne yükler.
+  -i, --ipfs=<value>           [varsayılan: https://ipfs.thegraph.com/api/v0] Derleme sonuçlarını bir IPFS düğümüne yükler.
   --ipfs-hash=<value>          Dağıtılacak subgraph manifestosunun IPFS hash değeri.
   --protocol-network=<option>  [varsayılan: arbitrum-one] Subgraph dağıtımı için kullanılacak ağı belirtir.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/tr/subgraphs/guides/near.mdx b/website/src/pages/tr/subgraphs/guides/near.mdx
index 134ad4c82262..bc1f80884c42 100644
--- a/website/src/pages/tr/subgraphs/guides/near.mdx
+++ b/website/src/pages/tr/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/tr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/tr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 60146e950eae..65a93164258c 100644
--- a/website/src/pages/tr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/tr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Bir Subgraph sorgulanırken her iki kimlik de kullanılabilir, ancak genellikle
 
 ## Dağıtım Kimliği
 
-Dağıtım Kimliği (Deployment ID), derlenmiş manifesto dosyasının IPFS hash’idir ve bilgisayardaki göreli URL’ler yerine IPFS üzerindeki diğer dosyalara referans verir. Örneğin, derlenmiş manifesto dosyasına şu bağlantı üzerinden erişilebilir: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. Dağıtım Kimliği’ni değiştirmek için, manifesto dosyasında güncelleme yapmak yeterlidir; örneğin, [Subgraph manifesto dokümantasyonu](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api)nda açıklandığı gibi "description" alanını değiştirerek bu sağlanabilir.
+Dağıtım Kimliği (Deployment ID), derlenmiş manifesto dosyasının IPFS hash’idir ve bilgisayardaki göreli URL’ler yerine IPFS üzerindeki diğer dosyalara referans verir. Örneğin, derlenmiş manifesto dosyasına şu bağlantı üzerinden erişilebilir: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. Dağıtım Kimliği’ni değiştirmek için, manifesto dosyasında güncelleme yapmak yeterlidir; örneğin, [Subgraph manifesto dokümantasyonu](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api)nda açıklandığı gibi "description" alanını değiştirerek bu sağlanabilir.
 
 Bir Subgraph'in Dağıtım Kimliği kullanılarak sorgu yapıldığında, sorgulanacak Subgraph sürümü açıkça belirtilmiş olur. Belirli bir Subgraph sürümünü sorgulamak için Dağıtım Kimliği kullanmak, sorgulanan sürüm üzerinde tam kontrol sağladığı için daha gelişmiş ve sağlam bir yapı sunar. Ancak, bu yaklaşım her yeni Subgraph sürümü yayımlandığında sorgu kodunun manuel olarak güncellenmesini gerektirir.
 
diff --git a/website/src/pages/uk/indexing/new-chain-integration.mdx b/website/src/pages/uk/indexing/new-chain-integration.mdx
index 670e06c752c3..d6815b2b832b 100644
--- a/website/src/pages/uk/indexing/new-chain-integration.mdx
+++ b/website/src/pages/uk/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 
diff --git a/website/src/pages/uk/indexing/overview.mdx b/website/src/pages/uk/indexing/overview.mdx
index 1ef3973c70cd..e2da100cbe73 100644
--- a/website/src/pages/uk/indexing/overview.mdx
+++ b/website/src/pages/uk/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/uk/indexing/tooling/graph-node.mdx b/website/src/pages/uk/indexing/tooling/graph-node.mdx
index edde8a157fd3..b535d6a471e7 100644
--- a/website/src/pages/uk/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/uk/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### IPFS Nodes
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Prometheus metrics server
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Getting started with Kubernetes
diff --git a/website/src/pages/uk/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/uk/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 2bc0ec5f514c..e3e3a7e3d455 100644
--- a/website/src/pages/uk/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/uk/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/uk/subgraphs/guides/near.mdx b/website/src/pages/uk/subgraphs/guides/near.mdx
index 792c41180f20..cedc744edba2 100644
--- a/website/src/pages/uk/subgraphs/guides/near.mdx
+++ b/website/src/pages/uk/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/uk/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/uk/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 17258dd13ea1..3b55aea5b072 100644
--- a/website/src/pages/uk/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/uk/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## Deployment ID
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/ur/indexing/new-chain-integration.mdx b/website/src/pages/ur/indexing/new-chain-integration.mdx
index ff1b5b6aa293..35a8e269c19e 100644
--- a/website/src/pages/ur/indexing/new-chain-integration.mdx
+++ b/website/src/pages/ur/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 
diff --git a/website/src/pages/ur/indexing/overview.mdx b/website/src/pages/ur/indexing/overview.mdx
index 8258c63fa6f1..22bc108de688 100644
--- a/website/src/pages/ur/indexing/overview.mdx
+++ b/website/src/pages/ur/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/ur/indexing/tooling/graph-node.mdx b/website/src/pages/ur/indexing/tooling/graph-node.mdx
index ca1535e89a01..19519b5e2022 100644
--- a/website/src/pages/ur/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/ur/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### IPFS نوڈس
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Prometheus میٹرکس سرور
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Kubernetes کے ساتھ شروع کریں
diff --git a/website/src/pages/ur/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/ur/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 0029f0a41559..6a8e4d17a9ff 100644
--- a/website/src/pages/ur/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/ur/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/ur/subgraphs/guides/near.mdx b/website/src/pages/ur/subgraphs/guides/near.mdx
index 325e114ac248..9d7ad9f8ef36 100644
--- a/website/src/pages/ur/subgraphs/guides/near.mdx
+++ b/website/src/pages/ur/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/ur/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/ur/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 3a51d42586d1..d9b9cbbc58d9 100644
--- a/website/src/pages/ur/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/ur/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## تعیناتی شناخت
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/vi/indexing/new-chain-integration.mdx b/website/src/pages/vi/indexing/new-chain-integration.mdx
index 670e06c752c3..d6815b2b832b 100644
--- a/website/src/pages/vi/indexing/new-chain-integration.mdx
+++ b/website/src/pages/vi/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ Configuring Graph Node is as easy as preparing your local environment. Once your
 
    > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+3. Run an IPFS node or use the one used by The Graph: https://ipfs.thegraph.com
 
 ## Substreams-powered Subgraphs
 
diff --git a/website/src/pages/vi/indexing/overview.mdx b/website/src/pages/vi/indexing/overview.mdx
index 034b74623eaf..88daf48cff6d 100644
--- a/website/src/pages/vi/indexing/overview.mdx
+++ b/website/src/pages/vi/indexing/overview.mdx
@@ -131,7 +131,7 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 - **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain Subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
 
-- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 - **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### Getting started using Docker
diff --git a/website/src/pages/vi/indexing/tooling/graph-node.mdx b/website/src/pages/vi/indexing/tooling/graph-node.mdx
index edde8a157fd3..b535d6a471e7 100644
--- a/website/src/pages/vi/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/vi/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ While some Subgraphs may just require a full node, some may have indexing featur
 
 ### IPFS Nodes
 
-Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during Subgraph deployment to fetch the Subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.thegraph.com.
 
 ### Prometheus metrics server
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Getting started with Kubernetes
diff --git a/website/src/pages/vi/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/vi/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index 2bc0ec5f514c..e3e3a7e3d455 100644
--- a/website/src/pages/vi/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/vi/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/vi/subgraphs/guides/near.mdx b/website/src/pages/vi/subgraphs/guides/near.mdx
index e78a69eb7fa2..34adc65f9175 100644
--- a/website/src/pages/vi/subgraphs/guides/near.mdx
+++ b/website/src/pages/vi/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Once your Subgraph has been created, you can deploy your Subgraph by using the `
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 The node configuration will depend on where the Subgraph is being deployed.
diff --git a/website/src/pages/vi/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/vi/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index 17258dd13ea1..3b55aea5b072 100644
--- a/website/src/pages/vi/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/vi/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deplo
 
 ## Deployment ID
 
-The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://ipfs.thegraph.com/ipfs/QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [Subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
 
 When queries are made using a Subgraph's Deployment ID, we are specifying a version of that Subgraph to query. Using the Deployment ID to query a specific Subgraph version results in a more sophisticated and robust setup as there is full control over the Subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the Subgraph is published.
 
diff --git a/website/src/pages/zh/indexing/new-chain-integration.mdx b/website/src/pages/zh/indexing/new-chain-integration.mdx
index 3083fd48bdbf..44dd25847ec5 100644
--- a/website/src/pages/zh/indexing/new-chain-integration.mdx
+++ b/website/src/pages/zh/indexing/new-chain-integration.mdx
@@ -63,7 +63,7 @@ title: 新链整合
 
    > 不要更改环境变量名称本身。它必须保持为 `ethereum` ，即使网络名称不同也是如此。  
 
-3. 运行IPFS节点，或使用Graph使用的IPFS节点： https://api.thegraph.com/ipfs/
+3. 运行IPFS节点，或使用Graph使用的IPFS节点： https://ipfs.thegraph.com
 
 ## Substreams驱动的子图
 
diff --git a/website/src/pages/zh/indexing/overview.mdx b/website/src/pages/zh/indexing/overview.mdx
index a20d5cb185d4..b2d640e79fe2 100644
--- a/website/src/pages/zh/indexing/overview.mdx
+++ b/website/src/pages/zh/indexing/overview.mdx
@@ -131,7 +131,7 @@ query indexerAllocations {
 
 - **数据端点**-对于兼容EVM的网络，Graph节点需要连接到一个公开兼容EVM JSON-RPC API的端点。这可以采取单个客户端的形式，也可以是跨多个客户端进行负载平衡的更复杂的设置。需要注意的是，某些子图将需要特定的客户端功能，如存档模式和/或奇偶校验跟踪API。
 
-- **IPFS 节点（版本小于 5）** - 子图部署元数据存储在 IPFS 网络上。 Graph节点在子图部署期间主要访问 IPFS 节点，以获取子图清单和所有链接文件。 网络索引人不需要托管自己的 IPFS 节点，网络的 IPFS 节点是托管在https://ipfs.network.thegraph.com。
+- **IPFS 节点（版本小于 5）** - 子图部署元数据存储在 IPFS 网络上。 Graph节点在子图部署期间主要访问 IPFS 节点，以获取子图清单和所有链接文件。 网络索引人不需要托管自己的 IPFS 节点，网络的 IPFS 节点是托管在https://ipfs.thegraph.com。
 
 - **索引人服务** -处理所有网络必要的外部通信。 共享成本模型和索引状态，将来自网关的查询请求传递给一个Graph节点，并通过状态通道与网关管理查询支付。
 
@@ -331,7 +331,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 #### 使用 Docker
diff --git a/website/src/pages/zh/indexing/tooling/graph-node.mdx b/website/src/pages/zh/indexing/tooling/graph-node.mdx
index b151102f4324..60432ec7d591 100644
--- a/website/src/pages/zh/indexing/tooling/graph-node.mdx
+++ b/website/src/pages/zh/indexing/tooling/graph-node.mdx
@@ -26,7 +26,7 @@ Graph节点的主存储区，这是存储子图数据、子图元数据以及子
 
 ### IPFS节点
 
-子图部署元数据存储在IPFS网络上。Graph节点主要在子图部署期间访问IPFS节点，以获取子图清单和所有链接文件。网络索引人不需要托管自己的IPFS节点。网络的IPFS节点托管于https://ipfs.network.thegraph.com。
+子图部署元数据存储在IPFS网络上。Graph节点主要在子图部署期间访问IPFS节点，以获取子图清单和所有链接文件。网络索引人不需要托管自己的IPFS节点。网络的IPFS节点托管于https://ipfs.thegraph.com。
 
 ### Prometheus指标服务器
 
@@ -66,7 +66,7 @@ createdb graph-node
 cargo run -p graph-node --release -- \
   --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
   --ethereum-rpc [NETWORK_NAME]:[URL] \
-  --ipfs https://ipfs.network.thegraph.com
+  --ipfs https://ipfs.thegraph.com
 ```
 
 ### Kubernetes入门
diff --git a/website/src/pages/zh/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/src/pages/zh/subgraphs/developing/publishing/publishing-a-subgraph.mdx
index f8a85bcfc0e7..97277b99a2ff 100644
--- a/website/src/pages/zh/subgraphs/developing/publishing/publishing-a-subgraph.mdx
+++ b/website/src/pages/zh/subgraphs/developing/publishing/publishing-a-subgraph.mdx
@@ -53,7 +53,7 @@ USAGE
 
 FLAGS
   -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  -i, --ipfs=<value>           [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.
   --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
   --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
                                <options: arbitrum-one|arbitrum-sepolia>
diff --git a/website/src/pages/zh/subgraphs/guides/near.mdx b/website/src/pages/zh/subgraphs/guides/near.mdx
index 05e59c328e6c..99ddaafa84ce 100644
--- a/website/src/pages/zh/subgraphs/guides/near.mdx
+++ b/website/src/pages/zh/subgraphs/guides/near.mdx
@@ -186,7 +186,7 @@ Subgraph Studio和The Graph网络上的升级索引人，目前支持在测试
 
 ```sh
 $ graph create --node <graph-node-url> <subgraph-name> # creates a Subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
-$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
+$ graph deploy --node <graph-node-url> --ipfs https://ipfs.thegraph.com <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the Subgraph to a specified Graph Node based on the manifest IPFS hash
 ```
 
 节点配置将取决于子图的部署位置。
diff --git a/website/src/pages/zh/subgraphs/querying/subgraph-id-vs-deployment-id.mdx b/website/src/pages/zh/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
index c715990d980a..44f2be9c3578 100644
--- a/website/src/pages/zh/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
+++ b/website/src/pages/zh/subgraphs/querying/subgraph-id-vs-deployment-id.mdx
@@ -10,7 +10,7 @@ Subgraph 是用Subgraph ID标明的，Subgraph 的每一版本都用部署ID标
 
 ## 部署 ID
 
-部署ID是编译清单文件的 IPFS 哈希值， 它是指IPFS上的其他文件，而不是计算机上的相对URL。 例如，编译后的清单可以访问：`https://api.thegraph。 om/ipfs/api/v0/cat?arg=QmQKXcNQRdUvNRMGJiE2idotu9fo5F5MRtKztH4WyKxED`。 要更改部署ID，只需更新清单文件， 例如修改描述字段如[子图文档](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api)。
+部署ID是编译清单文件的 IPFS 哈希值， 它是指IPFS上的其他文件，而不是计算机上的相对URL。 例如，编译后的清单可以访问：`https://ipfs.thegraph.com/ipfs/QmQKXcNQRdUvNRMGJiE2idotu9fo5F5MRtKztH4WyKxED`。 要更改部署ID，只需更新清单文件， 例如修改描述字段如[子图文档](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api)。
 
 当使用Subgraph的部署ID进行查询时，我们正在指定要查询的Subgra版本。 使用部署 ID 查询特定的 Subgraph 版本会导致更加复杂和强大的设置，因为正在查询的 Subgraph 版本的完全控制。 然而，这导致每次发布新版Subgra时，都需要手动更新查询码。