Floating IPs

IPv4 addresses for migrations and failover

IPv4 addresses you can move between your servers in the same region, for migrations and failover. Build high-availability architectures without DNS propagation delays.

Reassign Between Servers

Floating IP moving between two servers A Floating IP attached to one server and reassigned to a second server in the same region. Floating IP Reassign Server Server Same region
API managed
Self-service reverse DNS

MANRS-aligned · RPKI · Peered with 850+ networks

Why Floating IPs?

Reassign Between Servers

Move a Floating IP from one server to another via the dashboard or API. Nothing to configure inside the server: we add the address and announce it for you. No DNS propagation wait, no TTL expiry delays.

No DNS Propagation

Unlike changing A records, Floating IP reassignment happens at the network layer. The IP stays the same, only the target server changes.

AFRICLOUD IP Space

Floating IPs come from AFRICLOUD's own IP address space (AS209179). Consistent reputation, clean IP history, and no third-party dependencies.

API Managed

Create, assign, reassign, and release Floating IPs programmatically via the REST API. Automate failover in your deployment scripts and monitoring tools.

Self-Service Reverse DNS

Set the reverse DNS (PTR) record on each Floating IP yourself from the dashboard, ideal for mail servers and services that need matching forward and reverse records.

See AFRICLOUD in Action

Watch how easy it is to deploy and manage your server

Floating IP Explained: Failover Without DNS Changes

Built For

High Availability

Run primary and standby servers behind the same Floating IP. If the primary fails, reassign the IP to the standby server, with no DNS changes for your users to wait on.

  • Primary/standby failover
  • Reassign via dashboard or API
  • No DNS changes needed
  • Automate with API + monitoring

Blue/Green Deployments

Deploy new versions to a separate server, test them, then reassign the Floating IP to cut over. If something goes wrong, reassign it back to the previous version.

  • Cut over without DNS changes
  • Roll back by reassigning the IP
  • Test before switching
  • No DNS TTL delays

Load Balancing Failover

Use Floating IPs as the entry point for your load balancer. If the load balancer server fails, move the IP to a replacement without changing any client configurations.

  • Consistent entry point
  • Load balancer failover
  • Client-transparent recovery
  • API-driven automation

Ready for High Availability?

Reserve a Floating IP and assign it to your server. Move it to another server in the same region for migrations and failover, with no DNS changes.

Get Started

Have questions? Talk to us →