From 31309b217726bb4ebdb8182eb29d051a13ba1483 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Thu, 6 Feb 2025 12:04:28 +0100 Subject: [PATCH] feat(ins): add info that routed ip migration is complete --- pages/instances/how-to/migrate-routed-ips.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/pages/instances/how-to/migrate-routed-ips.mdx b/pages/instances/how-to/migrate-routed-ips.mdx index 20d9b78cd4..d18c325e95 100644 --- a/pages/instances/how-to/migrate-routed-ips.mdx +++ b/pages/instances/how-to/migrate-routed-ips.mdx @@ -7,12 +7,16 @@ content: paragraph: This page explains how to move your Instance to routed flexible IPs tags: instance flexible ip routed dates: - validation: 2024-11-14 + validation: 2025-02-06 posted: 2023-10-11 categories: - compute --- + + The migration to routed IPs is now complete. The following information is provided for reference only. + + Prior to April 2024, all Instances got a NAT IP from their hosting node, which was routed to the Instance through a [carrier-grade NAT](/instances/concepts/#carrier-grade-nat-cgnat) solution. This was in addition to the public (flexible) IP. The NAT IP let Instances communicate via an underlying internal network, without public IPs. However, if the underlying hypervisor changed, the NAT IP changed also. This could happen when you restarted your Instance. 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](/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.