Elastic IP is a public IP address you own independently of any cloud resource. Bind it to a Cloud Host, Load Balancer, NAT Gateway, or Virtual NIC — then move it to another resource in seconds, with no IP change and no service disruption. Pair it with a built-in gateway firewall, shared bandwidth pool, and flexible billing.
EIP gives you a permanent public IP address that works with any cloud resource — and the bandwidth, security, and billing controls to match your exact business model.
EIP separates your public IP address from the resource it's bound to — giving you full control over where your traffic lands, how much bandwidth you use, and what firewall rules apply. Here's exactly how it works.
Bind the EIP to a Cloud Host, Load Balancer, NAT Gateway, or Virtual NIC with a single click. Need to move it? Unbind from the current resource and rebind to another in seconds — with no IP change and no DNS update required. Your external services never notice anything changed.
EIP is not just an IP address — it's the complete public internet access layer for your cloud infrastructure, with bandwidth management, security, cost optimisation, and IP lifecycle management built in.
When your EIPs have traffic peaks at different times, buying maximum bandwidth for each individually is wasteful. Shared Bandwidth pools it — everyone draws from the same pool, and peaks average out.
Choose the billing mode that matches your traffic pattern. You can switch between modes at any time — the EIP address remains unchanged and your business keeps running.
From fast failover to cost-optimised multi-service bandwidth — EIP's flexibility shows up most in the scenarios where a fixed, tied IP would create friction.
When a Cloud Host fails, re-bind the EIP to a standby host in seconds. Users see no change — the public IP address remains the same, DNS records don't need updating, and SSL certificates stay valid. This is dramatically faster than waiting for DNS TTL to expire after pointing a domain to a new IP address.
You run a web service, an API endpoint, and a media delivery service — each with its own EIP. Their traffic peaks don't overlap: the web service peaks during business hours, the API at night, and the media service on weekends. Put all three EIPs in a shared bandwidth pool — one 80 Mbps pool covers what three separate 50 Mbps allocations would have needed, at a fraction of the cost.
Security teams can configure, update, copy, and apply firewall rules across all public-facing resources from the NubexCloud console — without logging into any individual server. Rules applied at the public network gateway are enforced before traffic reaches the host, consuming zero host CPU or memory. Update rules on 50 instances simultaneously with batch operations.
We had three payment API servers, each with its own EIP and its own 30 Mbps bandwidth allocation. The servers never all peaked at the same time. After switching to shared bandwidth, we run an 80 Mbps pool across all three — our total bandwidth cost dropped 38% and the APIs actually have more headroom during individual peaks than they did before.
We had a host failure during a product launch. With a standard IP tied to that host, we'd have had a DNS change and waited 15-30 minutes for propagation. With EIP, we unbound from the failed host and bound to our standby in under 30 seconds — users never noticed anything. The public IP and domain stayed identical throughout.
We manage 120 cloud servers for clients and needed consistent public firewall rule management. Previously we'd log into each server and apply iptables rules — slow and error-prone. Using NubexCloud's public firewall, we write a rule set once and batch-apply it to all 120 instances simultaneously. An update that used to take 3 hours now takes 5 minutes.
Elastic IP gives you a permanent public address that moves with your infrastructure — not against it. Failover in seconds. Bandwidth shared across services. Firewall at the gateway. All managed from one console.