fix(ins): details about routed IPv6

compute/instances/how-to/migrate-routed-ips.mdx

@@ -13,11 +13,11 @@ categories:
   - compute
 ---
 
-During deployment, each Instance gets a NAT IP from its hosting node, besides its public IP, which is routed to the Instance through a [carrier-grade NAT](/compute/instances/concepts/#carrier-grade-nat-(cgnat)) solution. However, if the underlying hypervisor changes, the NAT IP changes. This can happen when you restart your Instance. The NAT IP lets Instances communicate via an underlying internal network, without public IPs.
+During deployment, each Instance prior April 2024 used to get a NAT IP from its hosting node, besides its public IP, which is routed to the Instance through a [carrier-grade NAT](/compute/instances/concepts/#carrier-grade-nat-(cgnat)) solution. However, if the underlying hypervisor changes, the NAT IP changes. This can happen when you restart your Instance. The NAT IP lets Instances communicate via an underlying internal network, without public IPs.
 
-Routing a public IP directly to an Instance bypasses NAT IPs, sending traffic to its [routed flexible IP](/compute/instances/concepts/#routed-flexible-ip). The benefit is the IP stays consistent even if the Instance is restarted or moved. Routed IPs also let you assign multiple flexible IPv4s and IPv6s to an Instance, as both IPv4 and IPv6 are supported.
+Routing a public IP directly to an Instance bypasses NAT IPs, sending traffic to its [routed flexible IP](/compute/instances/concepts/#routed-flexible-ip). The benefit is the IP stays consistent even if the Instance is restarted or moved. Routed IPs also let you assign multiple flexible IPv4s and IPv6s to an Instance, as both IPv4 and IPv6 are supported (more on that bellow).
 
-Using a routed flexible IP is recommended for all compatible Instance types, as it allows precise control over network configurations. It simplifies troubleshooting, ensures compatibility with more applications, and allows for enhanced security monitoring.
+Using a routed flexible IP is recommended, as it allows precise control over network configurations. It simplifies troubleshooting, ensures compatibility with more applications, and allows for enhanced security monitoring.
 
 <Message type="important">
   * The routed IP feature **is incompatible** with legacy Instance types using the bootscript feature.
@@ -79,3 +79,8 @@ After the transition finishes, the notification icon will no longer be visible i
 </Message>
 
 
+## IPv6 support
+
+Routed IPs provide flexible IPv6 support. This means one can now assign an IPv6 that will remain the same whenever the Instance is located. Prior routed IPs, IPv6 were assigned per node location, thus whenever an Instance was relocated, its IPv6 was changed.
+However, for the best experience, your Instance must be supported (we won't provide support for EOL Operating Systems).
+For IPv6 only you need `cloud-init` version [23.2](https://github.com/canonical/cloud-init/releases/tag/23.2) or later and `scaleway-ecosystem` version 0.6 or later.