Use this file to discover all available pages before exploring further.
Updated May 8, 2026The Networking page in the dashboard opens to a live, interactive diagram of your private network: every VPC, every VM that lives in one, and every public IP attached to a VM, drawn in their actual relationships. It’s the fastest place to answer questions like “which VPC is this VM on?”, “which IP is attached to which server?”, and “can I detach this without breaking anything?” — and to take action without jumping between tabs.
When you enable an Internet Gateway on a VPC (see Manage a VPC → Internet Gateway), the diagram adds a Gateway card connected to the bottom of that VPC:
The Gateway card shows the two IPs that matter:
Line
What it means
🌐 Gateway
Header — the icon turns green when the gateway is active
Router IP (top, e.g. 10.7.0.1)
The gateway’s address inside the VPC. Always .1 of the VPC’s CIDR. VMs use this as their default gateway for outbound traffic
Public IP (bottom, e.g. 23.26.4.98)
The gateway’s WAN-side public IPv4. Outbound NAT and port-forwarding rules ride on this address
The Gateway card represents both gateway types — a Platform Router and a Firewall Appliance look identical here. To see which one is active, open the VPC’s detail page (the gateway card on that page tells you, and clicking the appliance VM in Compute confirms it). The diagram itself is intentionally simple — it’s the at-a-glance map, not the gateway control panel.The card appears the moment the gateway is enabled and disappears when you Disable it from the VPC detail page.
Releases the public IP from this VM. The IP returns to your account as unassigned — it isn’t deleted. Reassign it from the Public IPs tab.
Detaching a public IP disconnects any active SSH/RDP session routed through it. If the VM has no other public IP, it becomes reachable only from inside its VPC.
Removes the VM’s interface in this VPC. The VM stays running but loses the private IP from this VPC’s range.
A VM must remain reachable on at least one network — Raff blocks the detach if it would leave the VM with no interfaces. If the VM only has its VPC NIC and no public IP, attach a public IP first or move it to a different VPC before detaching.
The diagram answers the most common “what’s attached to what” questions at a glance:
VM with no public IP — no blue chip floats above the card. The VM is reachable only over its VPC.
VM with multiple public IPs — multiple chips stack above the card.
VM in multiple VPCs — the same VM card appears inside each VPC’s box, with its private IP from that VPC’s range.
VPC with no internet gateway — no Gateway card hangs below the VPC. VMs reach the internet only via their own public IPs.
VPC with internet gateway — a green Gateway card hangs below the VPC showing router IP and public IP — see above.
Empty VPC — green box with no VM cards. Safe to delete (or attach a VM with the VPC menu).
IP usage indicator — each VPC footer shows 1/253 IPs us-east style — number of IPs in use vs. total usable in the CIDR. Watch this when fleets grow toward the prefix’s limit.
