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.
zaphosting changed status to More Info Needed
Team•
Dec 29, 2025
Pinned
We love the direction, can you tell us a bit more? Any extra details help us understand what you’re aiming for.
aventis
•
Jan 18
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.
aventis
•
Dec 30, 2025
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.
Log in to comment and vote
Comments4
Jan 18
PinnedHey 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.
Dec 29, 2025
PinnedWe love the direction, can you tell us a bit more?
Any extra details help us understand what you’re aiming for.
aventis
Jan 18
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.
aventis
Dec 30, 2025
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.