scaleway · RoRoJ · Jul 1, 2025 · Jul 8, 2025 · Jul 10, 2025 · Jul 16, 2025
diff --git a/menu/navigation.json b/menu/navigation.json
@@ -4001,11 +4001,11 @@
               {
                 "items": [
                   {
-                    "label": "Order an InterLink",
+                    "label": "Create an InterLink",
                     "slug": "order-interlink"
                   },
                   {
-                    "label": "Complete InterLink provisioning",
+                    "label": "Complete hosted InterLink provisioning",
                     "slug": "complete-provisioning"
                   },
                   {

@@ -4,9 +4,9 @@ description: Understand Scaleway InterLink terminology with our glossary of the
 tags: interlink direct-connect dedicated self-hosted hosted connection
 dates:
   creation: 2024-10-31
-  validation: 2025-03-18
+  validation: 2025-08-29
 ---
-import image from './assets/scaleway-interlink-diag-simple.webp'
+import scalewayInterlinkDiagSimple from './assets/scaleway-interlink-diag-simple.webp'
 
 
 <Message type="note">
@@ -27,30 +27,36 @@ Every InterLink has a defined bandwidth, representing the maximum data transfer
 
 ## Connection type
 
-The type of physical connection for an InterLink. In the long term, InterLink will be available in both **hosted** and **self-hosted** connection types. For now, only **hosted** connections (facilitated via a partner) are available:
+The type of physical connection for an InterLink. InterLink is available in both **hosted** and **self-hosted** connection types:
 
-- **Hosted InterLink**:  The customer provisions an InterLink via a [partner](#partner). The available bandwidth of the partner's physical connection is shared between multiple customers: each gets a specified amount when creating their InterLink.
-- **Self-hosted InterLink**: The customer gets sole use of a single InterLink port on Scaleway's router, with the entire bandwidth of that port. They create their own dedicated physical connection, and can use its available bandwidth to provision several InterLinks for themselves.
+- **Hosted InterLink**:  The customer provisions an InterLink via a [partner](#partner), who facilitates the physical connection between the external infrastructure and the Scaleway VPC. The physical connection may be shared between several clients: each gets a specified amount when creating their InterLink.
+- **Self-hosted InterLink**: The customer provisions an InterLink using their own dedicated physical connection. They get the entire bandwidth of the connection, which can be used to provision several InterLinks for themselves.
 
 [Find out more about connection types](/interlink/reference-content/overview/#types-of-interlink).
 
+## Dedicated physical connection
+
+To create a self-hosted InterLink, you must first provision a dedicated physical connection between your router and Scaleway's router. You get sole use of a single InterLink port on Scaleway's router, with the entire bandwidth of that port. This connection and its bandwidth can then be used to create several InterLinks. To provision a dedicated physical connection, [contact our sales team](https://www.scaleway.com/en/contact-sales/).
+
+## Hosted InterLink
+
+See [connection type](#connection-type).
+
 ## InterLink
 
 InterLink, currently in Public Beta, is Scaleway's product to let you create a secure, private connection between your external infrastructure, and your Scaleway VPC. This allows you to direct your traffic safely from your Scaleway infrastructure to your on-premises infrastructure, away from the public internet.
 
-Currently, InterLink is available in **hosted** version only. This means that you must choose a compatible [partner](#partner) to facilitate the physical connection between the external infrastructure and the Scaleway VPC. The physical connection may be shared between several clients, each allocated a specific amount of bandwidth for their InterLink.
-
-<Lightbox image={image} alt="A diagram shows how a Scaleway VPC, to the left, can be attached to an InterLink, which then connects to external customer infrastructure." />
+<Lightbox image={scalewayInterlinkDiagSimple} alt="A diagram shows how a Scaleway VPC, to the left, can be attached to an InterLink, which then connects to external customer infrastructure." />
 
 For more information on how InterLink works, see our [detailed overview](/interlink/reference-content/overview/).
 
 ## Location
 
-A location, aka a **P**oint **o**f **P**resence (PoP), is a physical location where you can establish an InterLink between your on-premises infrastructure and the Scaleway network. Locations are facilitated by partners.
+A location, aka a **P**oint **o**f **P**resence (PoP), is a physical location where you can establish an InterLink between your on-premises infrastructure and the Scaleway network. For hosted InterLinks, locations are facilitated by partners.
 
 ## Pairing key
 
-A pairing key is a unique identifier used to establish and authenticate an InterLink via a partner. It is provided by Scaleway once an InterLink order is made. You must then share this key with your selected partner to facilitate the setup of the physical link. The pairing key ensures that the correct endpoints are securely connected.
+A pairing key is a unique identifier used to establish and authenticate a hosted link InterLink via a partner. It is provided by Scaleway once an InterLink order is made. You must then share this key with your selected partner to facilitate the setup of the physical link. The pairing key ensures that the correct endpoints are securely connected.
 
 ## Partner
 
@@ -68,10 +74,14 @@ When creating an InterLink, you must specify a [region](/vpc/concepts/#region-an
 
 ## Route propagation
 
-Route propagation can be activated or deactivated at any given time on an InterLink. When activated, the Scaleway VPC and external infrastructure dynamically exchange and update information about their routes. Route propagation must be activated to allow traffic to flow over the InterLink. When deactivated, all pre-learned/announced routes are removed from the VPC's route table, and traffic cannot flow. Note that even with route propagation activated, the default rule blocks all route announcements: you must attach a [routing policy](#routing-policy) to specify the route ranges to whitelist. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink)
+Route propagation can be activated or deactivated at any given time on an InterLink. When activated, the Scaleway VPC and external infrastructure communicate via BGP sessions to dynamically exchange and update information about their routes. Route propagation must be activated to allow traffic to flow over the InterLink. When deactivated, all pre-learned/announced routes are removed from the VPC's route table, and traffic cannot flow. Note that even with route propagation activated, the default rule blocks all route announcements: you must attach a [routing policy](#routing-policy) to specify the route ranges to whitelist. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink)
 
 ## Routing policy
 
 The default rule blocks any and all routes from being propagated over InterLink. Attaching a routing policy allows you to define the ranges of routes that should be whitelisted. When creating a routing policy, you specify one or many IP ranges representing the outgoing routes to announce from the Scaleway VPC, and one or many IP ranges representing the incoming route announcements to accept from the external infrastructure. 
 
-Each InterLink can have one routing policy attached to it, but a single routing policy can be attached to multiple InterLinks, if desired. When [route propagation](#route-propagation) is activated, the route ranges defined in the routing policy are whitelisted, and traffic can flow across the InterLink along these routes. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink)
+IPv4 and IPv6 routes must be whitelisted in separate routing policies. An InterLink must therefore have a **minimum of one** and a **maximum of two** attached routing policies, one for each IP traffic type to be routed (IPv4 and/or IPv6). When [route propagation](#route-propagation) is activated, the route ranges defined in the attached routing polic(ies) are whitelisted, and traffic can flow across the InterLink along these routes. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink).
+
+## Self-hosted InterLink
+
+See [connection type](#connection-type).
@@ -1,8 +1,8 @@
 ---
-title: InterLink FAQ
+title: InterLink
 description: Discover Scaleway InterLink and find answers to your most common questions.
 dates:
-  validation: 2025-03-18
+  validation: 2025-08-29
 productIcon: InterlinkProductIcon
 ---
 
@@ -14,21 +14,21 @@ InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/).
 
 InterLink is Scaleway's product to let you create a secure, private connection between your external infrastructure, and your Scaleway VPC. This allows you to direct your traffic safely from your Scaleway infrastructure to your on-premises infrastructure, away from the public internet.
 
-Currently, InterLink is available in **hosted** version only. This means that you must choose a compatible **partner** to facilitate your InterLink. The partner provides the physical connection, and this connection may be shared between several clients, each allocated a specific amount of bandwidth for their InterLink.
+Two types of InterLink are available: **hosted InterLink** where the physical connection is facilitated via a partner, or **self-hosted InterLink** where the customer provisions their own dedicated physical connection.
 
 At its simplest level, InterLink can be understood as a configurable connection between your own infrastructure, and your Scaleway VPC. You can configure details such as bandwidth, the VPC to connect to, and routing policies.
 
-## How can I find a partner to provision my InterLink?
+## How can I find a partner to provision my hosted InterLink?
 
 To establish a hosted InterLink via a partner, generally you must be a client of that partner, e.g. with your infrastructure in their data center, or on your own premises using the partner as a network provider. For more details, see our [information on choosing a partner](/interlink/reference-content/overview/#hosted-interlinks).
 
 You can see available partners in the Scaleway console by opening the [InterLink order form](https://console.scaleway.com/interlink/links/order). More partners will be added to Scaleway InterLink as time goes on.
 
 ## I want to create a dedicated InterLink without a partner, how can I do this?
 
-We plan to make **self-hosted** InterLinks available soon, whereby a single client can provision their own physical connection without a partner, getting sole use of a single InterLink port on Scaleway's router. The bandwidth of this connection can then be used by the client to create several InterLinks just for them.
+You can create a **self-hosted** InterLink, provisioning your own physical connection without a partner, getting sole use of a single InterLink port on Scaleway's router. You can then use the bandwidth of this connection to create several InterLinks just for you.
 
-You can [contact a sales representative](https://www.scaleway.com/en/contact-sales/) to register your interest in a self-hosted InterLink.
+[Contact a sales representative](https://www.scaleway.com/en/contact-sales/) to register your interest in a self-hosted InterLink. The process of provisioning the dedicated physical connection must be done via our sales team, and cannot be achieved via the Scaleway console or developer tools.
 
 ## What are the benefits of using InterLink compared to other connectivity solutions?
 

diff --git a/pages/interlink/how-to/assets/scaleway-interlink-overview.webp b/pages/interlink/how-to/assets/scaleway-interlink-overview.webp
@@ -1,41 +1,41 @@
 ---
-title: How to complete InterLink provisioning
+title: How to complete hosted InterLink provisioning
 description: Learn how to complete the provisioning process for your Scaleway InterLink, to ensure your hosted connection between your on-premises infrastructure and Scaleway VPC is up and running as soon as possible.
 dates:
-  validation: 2025-03-18
+  validation: 2025-08-29
   posted: 2025-03-18
 tags: interlink direct-connect provision hosted partner contact error
 ---
 import Requirements from '@macros/iam/requirements.mdx'
 
-import image from './assets/scaleway-interlink-ordering.webp'
-import image2 from './assets/scaleway-interlink-overview-requesting.webp'
-import image3 from './assets/scaleway-interlink-listing.webp'
+import scalewayHostedInterlinkOrdering from './assets/scaleway-hosted-interlink-ordering.webp'
+import scalewayInterlinkOverview from './assets/scaleway-interlink-overview.webp'
+import scalewayInterlinkListing from './assets/scaleway-interlink-listing.webp'
 
 
 <Message type="note">
 InterLink is currently in [Public Beta](https://www.scaleway.com/en/betas/).
 </Message>
 
-After you have [ordered your InterLink](/interlink/how-to/order-interlink), further action is required on both the customer side and the [partner](/interlink/concepts/#partner) side before the InterLink is provisioned and ready for active use. This page walks you through the steps to take and how to deal with potential problems that could arise.
+After you have [created a hosted InterLink](/interlink/how-to/order-interlink), further action is required on both the customer side and the [partner](/interlink/concepts/#partner) side before the InterLink is provisioned and ready for active use. This page walks you through the steps to take and how to deal with potential problems that could arise.
 
-<Lightbox image={image} alt="A four-step flow chart shows the following steps: 1. User orders InterLink via Scaleway, 2. User requests InterLink from partner, 3. Partner accepts InterLink request, 4. Partner provisions InterLink." />
+<Lightbox image={scalewayHostedInterlinkOrdering} alt="A four-step flow chart shows the following steps: 1. User orders InterLink via Scaleway, 2. User requests InterLink from partner, 3. Partner accepts InterLink request, 4. Partner provisions InterLink." />
 
 <Requirements />
 
 - A Scaleway account logged into the [console](https://console.scaleway.com)
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
-- [Ordered an InterLink](/interlink/how-to/order-interlink)
+- [Created a hosted InterLink](/interlink/how-to/order-interlink)
 
 ## Contact partner to request InterLink
 
-After ordering the InterLink from Scaleway, you **must** contact your chosen partner to request that they provision the connection on their side. Scaleway is not able to automatically do this step for you.
+After creating the hosted InterLink on the Scaleway side, you **must** contact your chosen partner to request that they provision the connection on their side. Scaleway is not able to automatically do this step for you.
 
 1. Click **InterLink** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. A listing of your InterLinks displays.
 
 2. Click on the InterLink that you want to finish provisioning. The InterLink's **Overview** page displays.
 
-<Lightbox image={image2} alt="A screen in the Scaleway console shows an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status." />
+    <Lightbox image={scalewayInterlinkOverview} alt="A screen in the Scaleway console shows an overview of an InterLink's partner, location, region, bandwidth, creation date, pairing key, and IPv4/IPv6 connectivity status." /> TODO UPDATE FROM CONSOLE
 
 3. Note down the [pairing key](/interlink/concepts/#pairing-key) for your InterLink. This is a unique identification number which the partner will need in order to provision your InterLink.
 
@@ -51,7 +51,7 @@ Your InterLink will remain in `Requested` status until the partner responds to y
 
 Once you have requested the InterLink from your partner, you must wait for them to respond to your request. There is no further action for you to take at this point. You can keep track of your InterLink's [status](/interlink/reference-content/statuses/) via the [InterLink listing](https://console.scaleway.com/interlink/links) in the Scaleway console.
 
-<Lightbox image={image3} alt="A screen in the Scaleway console shows a listing of InterLinks, with the following information: name, status, partner, location, region and bandwidth." />
+<Lightbox image={scalewayInterlinkListing} alt="A screen in the Scaleway console shows a listing of InterLinks, with the following information: name, status, partner, location, region and bandwidth." /> TODO UPDATE
 
 When the partner approves your request, the InterLink moves to `Provisioning` status. This means that the partner has agreed to facilitate your InterLink, and is now preparing the resources and configuration necessary to do so.