Skip to content
Feature RequestNotificationsOpen

Floating IP (VIP)

I would like to have floatings ips so the IP addresses that in the moment must add to a server can use also on other Server. In the moment it get a abuse notification when try this.

Originally posted by aventis on our previous feedback board.

Ffeaturebase-import27 Dec 2025

Comments (4)

ZAP
Official response
29 Dec 2025, 01:50

We love the direction, can you tell us a bit more? Any extra details help us understand what you’re aiming for.

F
featurebase-import30 Dec 2025, 22:44

A Floating IP can be ordered in a similar way to an IP for a dedicated server, but it is not permanently bound to a specific server. Instead, the Floating IP is assigned to the account. The Floating IP can then be moved between servers using one of the following methods: ARP-based assignment The server that should use the Floating IP sends an ARP (Address Resolution Protocol) request, allowing the IP to be associated with that server at the network level. API-based assignment An API call is used to explicitly assign the Floating IP to a specific server.

Originally posted by aventis on our previous feedback board.

ZAP
Official response
18 Jan 2026, 02:17

Hey there, thanks for the suggestion about floating IPs. Unfortunately, this isn't something we can implement. We regularly move subnets between different locations to manage demand, which makes static, movable IPs unfeasible. Also, for privacy and network management reasons, we can't permanently assign a single IP to one customer forever to the point where it could be a floating IP on the account.

F
featurebase-import18 Jan 2026, 22:59

Thanks for the answer! I get that some things might not be possible for various reasons, but the reason is not possible for me. I have three dedicated servers with IPs assigned at the server level, which I consider as fixed. When these IPs change without me knowing, my whole infrastructure (cluster) stops working. I believe these “fixed IPs” shouldn’t be tied just to the server level but managed at the account level. This way, they could be changed via API or ARP requests to different servers, which would help with hyperconvergence and make things easier to manage. Right now, a workaround could be using a VM with Open vSwitch, but that creates a single point of failure since all traffic would have to go through it.

Originally posted by aventis on our previous feedback board.

Log in to comment.

Timeline

No timeline entries yet.

Changes here will appear in this timeline.

Feedback

Do you have another suggestion?