fix(instances): more info

Author: RoRoJ

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

@@ -13,11 +13,11 @@ categories:
   - compute
 ---
 
-Prior to April 2024, Scaleway Instances got a NAT IP from their hosting node, in addition to their public IP. This NAT IP was routed to the Instance through a [carrier-grade NAT](/compute/instances/concepts/#carrier-grade-nat-(cgnat)) solution. However, if the underlying hypervisor changed, the NAT IP also changed. This could happen when you restarted your Instance. The NAT IP let Instances communicate via an underlying internal network, without public IPs.
+Prior to April 2024, all Scaleway Instances got a NAT IP from their hosting node, in addition to their public IP. This NAT IP was routed to the Instance through a [carrier-grade NAT](/compute/instances/concepts/#carrier-grade-nat-(cgnat)) solution. However, if the underlying hypervisor changed, the NAT IP also changed. This could happen when you restarted your Instance. The NAT IP let Instances communicate via an underlying internal network, without public IPs.
 
-Instances created since April 2024 no longer have NAT IPs, but instead their public IPs are **routed** 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.
+Since October 2024 it is no no longer possible to create Instances with NAT IPs. Instead, Instances' public IPs are **routed** 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.
 
-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. Users with Instances created prior to April 2024 are invited to move to routed IPs by following the instructions below.
+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. Users with Instances still using NAT IPs are invited to move them to routed IPs by following the instructions below.
 
 <Message type="important">
   * The routed IP feature **is incompatible** with legacy Instance types using the bootscript feature.