Skip to content

feat(ins): add info that routed ip migration is complete #4365

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 6, 2025
Merged

feat(ins): add info that routed ip migration is complete #4365

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion pages/instances/how-to/migrate-routed-ips.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
---

<Message type="note">
The migration to routed IPs is now complete. The following information is provided for reference only.
</Message>

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.
Expand Down