Floating IPs
Beta. Floating IPs are enabled for qualified teams and VPS hosts. The console shows only configured locations. Availability depends on address capacity and host compatibility.
Floating IPs are additional public IPv4 or IPv6 addresses that belong to your team independently of a VPS. Reserve an address, assign it to one eligible VPS, and reassign it later while keeping the address. Your VPS keeps its primary addresses.
Each Floating IPv4 is one /32 address. Each Floating IPv6 is one /128 address, not a /64 subnet.
Reserve and assign an address
- Open Floating IPs in the console sidebar, then choose Add Floating IP.
- Enter a name, choose IPv4 or IPv6, and select an available location. You can add up to 20 labels as
key=valuepairs. - Review the price shown in the drawer, excluding VAT, then reserve the address. Charging starts at reservation and continues while the address is unassigned.
- Open Manage for the address and choose a running VPS in your team and the same network zone. It must already have a primary IP of the matching type.
- Choose Assign Floating IP and wait for Routing applied. Then configure the address inside the guest operating system as described below.
An address can be assigned to only one VPS at a time. The default limits are 10 Floating IPs per team and 20 per VPS. Your account's approved limit may differ; the console shows your team limit. Contact support to request more capacity.
The VPS does not need a shutdown for the network assignment. Routing applied confirms our network configuration; it does not confirm that your guest or application has configured the address.
Configure the address inside a Linux VPS
Keep the primary address and its existing default gateway. Add the Floating IP as an additional address on the same public interface.
First identify your public interface:
ip -br address
ip -4 route show default
ip -6 route show default
Look for the interface holding the VPS's primary address. Use its actual name in place of PUBLIC_INTERFACE below. Use your reserved Floating IP in place of FLOATING_IPV4 or FLOATING_IPV6.
For IPv4:
sudo ip address add FLOATING_IPV4/32 dev PUBLIC_INTERFACE
ip -4 address show dev PUBLIC_INTERFACE
For IPv6:
sudo ip -6 address add FLOATING_IPV6/128 dev PUBLIC_INTERFACE
ip -6 address show dev PUBLIC_INTERFACE
These commands are temporary and do not survive a reboot. To persist the address, add it to the existing network configuration for that interface, using your distribution's network manager, such as Netplan, NetworkManager, systemd-networkd or /etc/network/interfaces. Preserve the primary address, DHCP settings, routes and gateway. Use the network manager's safe apply or rollback facility when changing a remote VPS.
Ensure your application listens on the additional address or on all appropriate interfaces, and that your VPS firewall allows the intended traffic. Test from another machine using the assigned Floating IP. If routing is applied but the service is unreachable, check guest addresses, listening sockets and firewall rules first.
Reassign without changing the address
Before reassigning, remove the Floating IP from the old guest and configure it on the destination guest. The address must not remain configured on both guests.
# IPv4: run inside the old VPS
sudo ip address delete FLOATING_IPV4/32 dev PUBLIC_INTERFACE
# IPv6: run inside the old VPS
sudo ip -6 address delete FLOATING_IPV6/128 dev PUBLIC_INTERFACE
Remove the corresponding persistent configuration from the old guest too. Open Manage, choose the destination VPS, and select Reassign Floating IP. Wait for Routing applied, add the address on the destination guest, and verify connectivity. Plan for an interruption while guest and network configuration change.
The console displays the requested VPS and the last confirmed VPS separately while an assignment is in progress. If a network change fails, Manage offers assignment or unassignment retry. Contact support if the retry fails.
Unassign and release
Unassign removes the network assignment and preserves your reservation. The address remains billable. Remove the temporary and persistent address configuration from the old guest.
To stop charging:
- Unassign the address.
- Wait until cleanup is confirmed and Release address becomes available.
- Confirm Release address. Billing ends after the release succeeds.
A released address may be allocated to another customer. You may not be able to reserve the same address again. A failed or unfinished unassignment does not make an address available for release.
Gateway availability
Existing subnet addresses are routed through the host that owns their subnet, even when the VPS runs on a different host. That gateway remains in the traffic path. A gateway outage can interrupt Floating IP connectivity while the VPS itself remains running. Floating IP reassignment changes the destination VPS; it does not move the provider's subnet gateway.
API
The API uses /api/v1/floating-ips and dedicated token abilities:
| Ability | Operations |
|---|---|
floating-ips:read | List and inspect addresses |
floating-ips:write | Reserve, edit, assign and unassign |
floating-ips:delete | Release after confirmed cleanup |
Create with name, ip_version (4 or 6), datacenter and optional labels. Address selection and subnet placement are managed by the platform. Assignment, unassignment and release requests must include the expected_generation from the most recent resource response. Assignments also require vps_instance_id.
Assignment responses distinguish desired and applied generations and VPS IDs. A successful assignment request means the change was accepted; poll the resource until the applied generation matches and its state is settled. Guest configuration is still required.