vRack Public Bandwidth

pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-asia.md

@@ -1,7 +1,7 @@
 ---
-title: Configuring an IPv6 block in a vRack
+title: Configuring an Additional IPv6 block in a vRack
 excerpt: Find out how to configure a block of public IPv6 addresses for use with an OVHcloud vRack network
-updated: 2025-06-04
+updated: 2026-03-13
 ---
 
 <style>
@@ -44,15 +44,15 @@ The vRack network serves as a global private network bridging various OVHcloud p
 
 ## Introduction
 
-IPv6 revolutionizes networking within OVHcloud's vRack by addressing IPv4's limitations and introducing features for the modern internet. Its rollout is a direct response to the need for more extensive, secure, and sophisticated internet architectures. Here are the key benefits of integrating IPv6 with vRack:
+IPv6 revolutionizes networking within OVHcloud's vRack by addressing IPv4's limitations and introducing features for the modern Internet. Its rollout is a direct response to the need for more extensive, secure, and sophisticated Internet architectures. Here are the key benefits of integrating IPv6 with vRack:
 
 - **Flexibility for Advanced Networking**: IPv6 significantly increases the address space, providing the flexibility needed to scale infrastructure, manage failover scenarios and support larger solutions. This ensures that networks can grow and adapt without the space constraints of IPv4.
 
 - **Hierarchical Routing and Segmentation**: IPv6 enables efficient hierarchical routing and logical infrastructure segmentation. This improves network manageability and security, ideal for reselling VMs with dedicated subnets or organising infrastructure into distinct segments.
 
 - **Low latency**: Native, end-to-end IPv6 connectivity can be an enabler for latency-sensitive services like media streaming, as many recent provider networks are built IPv6-native. In such networks, using IPv4 services brings additional latency (and costs).
 
-By leveraging IPv6 within vRack, OVHcloud users can enjoy a more secure, efficient, and scalable network environment, ready to meet the demands of modern internet usage.
+By leveraging IPv6 within vRack, OVHcloud users can enjoy a more secure, efficient, and scalable network environment, ready to meet the demands of modern Internet usage.
 
 
 ## Requirements
@@ -204,6 +204,65 @@ Don't forget to configure SLAAC on your host machine.
 
 ///
 
+### Managing public IP bandwidth on vRack
+
+By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5 Gbps in Europe/Canada/US and 100 Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). 
+
+As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. Note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region.
+
+/// details | During the Additional IP ordering process
+
+#### Choosing public bandwidth during an Additional IP order
+
+The default public bandwidth can be changed when ordering a new Additional IP block with a vRack network as the backend.
+
+To order a new Additional IPv6 block:
+
+- Log in to the [OVHcloud Control Panel](/links/manager).
+- Open the `Network`{.action} section in the left-hand sidebar.
+- Select `Public IP addresses`{.action}.
+- Click on the `Order IPs`{.action} button, near the top of the page.
+- Select the IP version, then the vRack you want to attach your Additional IP to.
+- Select the region you want your Additional IP to be in.
+- Choose the public bandwidth you want to apply to your vRack for that specific region.
+- Fill in the other options as necessary, then proceed with your order.
+
+///
+
+/// details | From the vRack management page
+
+#### Modifying vRack public bandwidth on management page
+
+For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page.
+
+To access the management interface:
+
+- Open `Network`{.action} in the left-hand sidebar of your Control Panel.
+- Select `vRack private network`{.action}.
+- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack.
+
+The management page is organized into two tabs:
+
+- **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way.
+- **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth.
+
+To modify the public bandwidth:
+
+- Navigate to the `Public IP routing`{.action} tab.
+- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region.
+- Within the window for the relevant region, click the `Modify bandwidth`{.action} button.
+- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order.
+- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes.
+
+> [!primary]
+>
+> Charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle.
+>
+
+The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack.
+
+///
+
 #### Host-side commands
 
 /// details | Static IP configuration
@@ -552,7 +611,7 @@ Understanding the constraints of using **Additional IPv6** within the **vRack**
 - **SLAAC limitations in multi-location setups**: Stateless Address Autoconfiguration (SLAAC) is not supported when there is public IP traffic (both IPv6 and IPv4) routed into vRack in multiple region locations.
 - **Up to 128 hosts inside bridged subnet**: You can use up to 128 IP addresses directly on the vRack.
 - **Up to 128 next-hop routes**: You can use up to 128 routes for routed subnets inside a vRack.
-- **Public bandwidth cap**: Outbound traffic from OVHcloud to the internet is capped at 5Gbps per region location.
+- **Public bandwidth cap**: Outbound traffic from OVHcloud to the Internet is capped at 5 Gbps per region location.
 - **IPv6 block allocation limits**: Single Additional IPv6 block per vRack in a region location. Maximum of 3 blocks (/56) per region location.
 - **Mobility of Additional IPv6 blocks**: Due to the hierarchical design of the IPv6 address space, Additional IPv6 blocks are region-specific. This means blocks cannot be transferred between regions, although they can be reassigned within any vRack-connected backend.
 - **No direct VLAN 802.1Q support in vRack by Additional IPv6**: Configuration can only be done with native VLAN of your vRack network. For packet forwarding inside specific VLAN (of a vRack) a dedicated host on customer side will be needed.

pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-in-a-vrack/guide.en-au.md

@@ -1,7 +1,7 @@
 ---
-title: Configuring an IPv6 block in a vRack
+title: Configuring an Additional IPv6 block in a vRack
 excerpt: Find out how to configure a block of public IPv6 addresses for use with an OVHcloud vRack network
-updated: 2025-06-04
+updated: 2026-03-13
 ---
 
 <style>
@@ -44,15 +44,15 @@ The vRack network serves as a global private network bridging various OVHcloud p
 
 ## Introduction
 
-IPv6 revolutionizes networking within OVHcloud's vRack by addressing IPv4's limitations and introducing features for the modern internet. Its rollout is a direct response to the need for more extensive, secure, and sophisticated internet architectures. Here are the key benefits of integrating IPv6 with vRack:
+IPv6 revolutionizes networking within OVHcloud's vRack by addressing IPv4's limitations and introducing features for the modern Internet. Its rollout is a direct response to the need for more extensive, secure, and sophisticated Internet architectures. Here are the key benefits of integrating IPv6 with vRack:
 
 - **Flexibility for Advanced Networking**: IPv6 significantly increases the address space, providing the flexibility needed to scale infrastructure, manage failover scenarios and support larger solutions. This ensures that networks can grow and adapt without the space constraints of IPv4.
 
 - **Hierarchical Routing and Segmentation**: IPv6 enables efficient hierarchical routing and logical infrastructure segmentation. This improves network manageability and security, ideal for reselling VMs with dedicated subnets or organising infrastructure into distinct segments.
 
 - **Low latency**: Native, end-to-end IPv6 connectivity can be an enabler for latency-sensitive services like media streaming, as many recent provider networks are built IPv6-native. In such networks, using IPv4 services brings additional latency (and costs).
 
-By leveraging IPv6 within vRack, OVHcloud users can enjoy a more secure, efficient, and scalable network environment, ready to meet the demands of modern internet usage.
+By leveraging IPv6 within vRack, OVHcloud users can enjoy a more secure, efficient, and scalable network environment, ready to meet the demands of modern Internet usage.
 
 
 ## Requirements
@@ -204,6 +204,65 @@ Don't forget to configure SLAAC on your host machine.
 
 ///
 
+### Managing public IP bandwidth on vRack
+
+By default, Additional IP blocks routed via a vRack benefit from a standard public bandwidth of 5 Gbps in Europe/Canada/US and 100 Mbps in APAC regions. For a detailed overview of availability, please refer to public routing options on our [vRack product page](/links/network/vrack). 
+
+As infrastructure requirements scale, users may require broader bandwidth to support high-traffic public-oriented services, for which OVHcloud provides paid bandwidth options. Note that bandwidth options are applied **per-vRack and per-region**. Since Additional IP addresses are tied to a region, any bandwidth modification will affect all IP addresses (both IPv4 and IPv6) routed to the specific vRack within that particular region.
+
+/// details | During the Additional IP ordering process
+
+#### Choosing public bandwidth during an Additional IP order
+
+The default public bandwidth can be changed when ordering a new Additional IP block with a vRack network as the backend.
+
+To order a new Additional IPv6 block:
+
+- Log in to the [OVHcloud Control Panel](/links/manager).
+- Open the `Network`{.action} section in the left-hand sidebar.
+- Select `Public IP addresses`{.action}.
+- Click on the `Order IPs`{.action} button, near the top of the page.
+- Select the IP version, then the vRack you want to attach your Additional IP to.
+- Select the region you want your Additional IP to be in.
+- Choose the public bandwidth you want to apply to your vRack for that specific region.
+- Fill in the other options as necessary, then proceed with your order.
+
+///
+
+/// details | From the vRack management page
+
+#### Modifying vRack public bandwidth on management page
+
+For Additional IP blocks already attached to a vRack, bandwidth can be managed directly through the service configuration page.
+
+To access the management interface:
+
+- Open `Network`{.action} in the left-hand sidebar of your Control Panel.
+- Select `vRack private network`{.action}.
+- In the "Public IP & bandwidth" column, click the `Manage`{.action} button for the corresponding vRack.
+
+The management page is organized into two tabs:
+
+- **All attached services**: For the time being, it redirects to the classic vRack management page. Soon, it will list all the products (Servers, Cloud Projects, etc.) currently linked to the vRack, in a new way.
+- **Public IP routing**: Manages the public IP routing options of your vRack, including public bandwidth.
+
+To modify the public bandwidth:
+
+- Navigate to the `Public IP routing`{.action} tab.
+- The interface displays individual management windows for each region (e.g., `eu-west-par`) associated with the vRack, listing all IP addresses attached to that specific region.
+- Within the window for the relevant region, click the `Modify bandwidth`{.action} button.
+- Select the desired bandwidth option in the panel that appears on the right-hand side, then click `Proceed to order`{.action} to validate the order.
+- Once paid, the selected bandwidth should be available to your vRack in the chosen region after a few minutes.
+
+> [!primary]
+>
+> Charges for the initial month are pro-rated based on the remaining days, with the full rate effective the next billing cycle.
+>
+
+The selected bandwidth upgrade will apply to all IP addresses in that region for the chosen vRack.
+
+///
+
 #### Host-side commands
 
 /// details | Static IP configuration
@@ -552,7 +611,7 @@ Understanding the constraints of using **Additional IPv6** within the **vRack**
 - **SLAAC limitations in multi-location setups**: Stateless Address Autoconfiguration (SLAAC) is not supported when there is public IP traffic (both IPv6 and IPv4) routed into vRack in multiple region locations.
 - **Up to 128 hosts inside bridged subnet**: You can use up to 128 IP addresses directly on the vRack.
 - **Up to 128 next-hop routes**: You can use up to 128 routes for routed subnets inside a vRack.
-- **Public bandwidth cap**: Outbound traffic from OVHcloud to the internet is capped at 5Gbps per region location.
+- **Public bandwidth cap**: Outbound traffic from OVHcloud to the Internet is capped at 5 Gbps per region location.
 - **IPv6 block allocation limits**: Single Additional IPv6 block per vRack in a region location. Maximum of 3 blocks (/56) per region location.
 - **Mobility of Additional IPv6 blocks**: Due to the hierarchical design of the IPv6 address space, Additional IPv6 blocks are region-specific. This means blocks cannot be transferred between regions, although they can be reassigned within any vRack-connected backend.
 - **No direct VLAN 802.1Q support in vRack by Additional IPv6**: Configuration can only be done with native VLAN of your vRack network. For packet forwarding inside specific VLAN (of a vRack) a dedicated host on customer side will be needed.