Floating IPs. Portable addresses.

IP addresses that can be reassigned between servers in the same region in under 5 seconds via API. Build high-availability architectures, zero-downtime failover, and blue-green deployments without DNS propagation delays.

<5s
Reassignment
API
Managed
IPv4
+ IPv6
rDNS
Control
How It Works

Instant IP reassignment

A floating IP is a public IP address that isn't tied to a specific server. It exists as a resource in your account and can be pointed at any server in the same region. When you reassign it, the change takes effect at the network level within seconds — no DNS propagation, no TTL waiting.

Under the hood, reassignment updates the ARP mapping and routing table entries on our network infrastructure. The IP address moves from one server's network port to another. New connections to the floating IP will reach the new server immediately.

This is fundamentally different from DNS-based failover, which depends on resolvers respecting TTL values and can take minutes or hours to fully propagate.

High Availability
Floating IP — Active-Passive Failover Reassign a public IP between servers in under 5 seconds — no DNS propagation needed NORMAL Users / Traffic Connecting to 203.0.113.50 203.0.113.50 FLOATING IP Server A Active · serving traffic 10.0.0.1 (private) Server B Passive · standby 10.0.0.2 (private) < 5s FAILOVER Users / Traffic Same IP: 203.0.113.50 203.0.113.50 REASSIGNED Server A Failed · IP removed 10.0.0.1 (private) Server B Now active · serving 10.0.0.2 (private) Failure detected Health check fails API call Reassign floating IP < 5 seconds Traffic on new server Network-level reassignment · no DNS propagation · no TTL waiting

Active-passive failover

The most common pattern is an active-passive pair. Two servers run the same application — the active server holds the floating IP and serves all traffic. A health check script monitors the active server. If it fails, the script reassigns the floating IP to the passive server via a single API call.

The API call to reassign takes about 200ms, and the IP is reachable on the new server within 5 seconds. For stateful applications, combine floating IPs with replicated storage so the passive server has current data when it takes over.

Move IPs in seconds. No DNS wait.

Blue-Green

Zero-downtime deployments

Deploy a new version to a standby server. Run smoke tests against its direct IP. Then reassign the floating IP from the current server to the new one. All new traffic hits the new version immediately. If something goes wrong, reassign back — rollback takes the same 5 seconds.

This pattern works for any application — web servers, APIs, databases, game servers. The only requirement is that both servers are in the same region.

Details

Technical details

Floating IPs are available in both IPv4 and IPv6. Each costs $3/month (prorated hourly). Reverse DNS (PTR records) can be set via API for email deliverability. You can hold unassigned IPs for future use.

Features
Instant Reassign
Move a floating IP between servers in under 5 seconds via a single API call.
<5s
No DNS Wait
Changes take effect at the network level. No TTL expiry, no resolver caching issues.
Network
Dual Stack
Available in IPv4 and IPv6. Assign one or both per server. Each billed independently.
IPv4+v6
Reverse DNS
Set custom rDNS (PTR) records on floating IPs for email deliverability and identification.
rDNS
API + Terraform
Create, assign, unassign, and destroy floating IPs programmatically. Full automation support.
REST
Regional
Floating IPs can be reassigned to any server in the same region. Cross-region not supported.
Per-region

Get a floating IP.

$3/mo. Instant reassignment. API managed.