Reserved IP

A reserved IP is a public IPv4 address that belongs to your account rather than to one resource. It stays yours until you delete it, even after the node it was attached to is gone. A domain, a partner’s allow list, or a client with a fixed address can keep pointing at it while you change what sits behind it.

Say you move a website to a new node on a different plan. If the site’s DNS record points at a reserved IP, you attach that address to the new node and the site answers there, with no DNS change to wait for.

A reserved IP can do three jobs:

• A node’s primary public IP, chosen when you create the node or attached later.
• An Add-on IP: a second public address on a node or a Firewall, next to the one it already has.
• A Floating IP: one address shared by up to four nodes, so a service can fail over from one node to another without its address changing.

What you can do with a reserved IP

• Reserve an IP, fresh from the pool or by keeping the public IP a resource already has.
• Attach a reserved IP as an Add-on IP to a node or a firewall.
• Attach a reserved IP to a node as its primary public IP.
• Use a reserved IP as a Floating IP, then set up failover with a Floating IP.
• Reserve a node’s public IP when you delete it.
• Move a reserved IP to another project.
• Request a higher reserved IP limit.
• Delete a reserved IP.

Where to start

Get started with Reserved IP reserves an address and attaches it to a node. Reserved and Floating IPs explains the two modes and what each status means.