Flexible Traffic Management
Floating IP addresses are independent of the server lifecycle. When you replace a server, simply move the IP to the new one; your customers notice nothing and there is no DNS propagation wait.
Replace servers while your IP address and DNS records stay the same
Regions: tr-ist-01 (İstanbul) · tr-ank-01 (Ankara).
Internet traffic and the DNS record target a single persistent public IP.
When instance A fails its binding to the IP is dropped; the address is still yours.
The IP is re-associated to standby instance B from the console or the API.
The DNS record is untouched; traffic reaches the new owner without waiting for caches to expire.
Answer
A Floating IP is a static public address you move between resources. You shift traffic without changing the DNS record.
Cost depends on allocated ip and usage duration, attached resource lifecycle, traffic and data transfer. Review the current estimate in the cost calculator.Calculate Cost
Live capacity and quota depend on the selected resource; service level terms are explained on the SLA page.
Features
How it works
Floating IP addresses are independent of the server lifecycle. When you replace a server, simply move the IP to the new one; your customers notice nothing and there is no DNS propagation wait.
A Floating IP is used in two steps. First, allocate an address from Network > Floating IP with "New Floating IP"; the console allocates it through a single confirmation dialog and reserves the address from the pool for your account. Then attach it to a server: the "Associate Floating IP" entry in the action menu on the instance detail page maps the allocated address to the server's port on the private network. The same menu disassociates it so the address can move to another server. For the address to work, the server's subnet must be attached to a router with NAT enabled; the "Enable NAT" option in the router creation dialog grants exactly that.
In failover you move the address to the standby server. DNS, allow-lists and integration endpoints stay the same. To keep distributing traffic across several servers, give the address to a Load Balancer.
PortvMind Cloud operates the address pool, routing of the address through the Router and the NAT layer. Which server the address is attached to, which ports that server's Security Group exposes, the operating-system firewall and the DNS records belong to your team. A public address is reachable from the internet, so leave only the required ports open in the Security Group before associating it, for example 443. Presets such as "HTTPS" fill the port and source range automatically.
How many addresses you can allocate depends on your account quota and is shown under Quota. For the address to carry traffic, the server subnet must be attached to a router with NAT enabled. The setup order is Router, subnet attachment, then Floating IP.
Scenarios
Decision criteria
Hover or press play; the steps light up in time with the recording.
FAQ
Create an account in the console, complete email, phone and card verification, then open your first virtual server in Compute. Use calculator.portvmind.com to plan the cost.
PortvMind Cloud uses a pay-as-you-go model with per-minute billing. Total cost depends on resource type, selected configuration, storage, network and runtime. Current unit prices are in the console and at calculator.portvmind.com.
Next step
Create the resource in the console. For a migration or scaling plan, continue together in an architecture consultation.
Model your scenario in the cost calculator.Calculate Cost