Open the load balancer → Network tab in my.cubepath.com.
Shows both sides of the load balancer's connectivity.
Floating IPs
The public IPv4 and IPv6 addresses assigned to the load balancer. This is the address your DNS points at, and the one clients connect to.
Because these are floating IPs, they belong to your organization rather than to this load balancer, so the public address survives a rebuild and DNS never has to change.
NoteA load balancer with no floating IP assigned isn't reachable from the internet. Assign one in Settings.
Private network
The private network the load balancer is attached to, if any. With one attached, the load balancer reaches its backends over private addresses.
That's the configuration you want for anything sensitive: the backends need no public IP at all, so they can't be reached directly, and the only way in is through the load balancer's listeners and health checks.
ImportantTargets must be on the same private network as the load balancer. A server on a different network — or on none — can't be reached over private addressing.
If those backends also need outbound internet access (package updates, external APIs), pair the private network with a NAT Gateway. Together they give you servers that can reach out but can't be reached.