Public IPv6
Every VM gets its own routed public IPv6 /64, free, with a usable address configured from the first boot. There's no NAT on IPv6: traffic is routed straight to the VM.
How it works
- Free — no charge for the prefix or its addresses.
- A whole /64 per VM — the VM starts with one address in it. You can configure more addresses from the same /64 in the guest without registering them.
- Stable — the prefix stays with the VM across stop/start, restart, and resize. Deleting the VM releases it.
- Independent of IPv4 — a VM can have IPv6 only, or IPv6 plus one or more public IPv4s.
Reaching your VM over IPv6
The VM's overview shows its IPv6 address. From an IPv6-capable client:
ssh ubuntu@2606:2a80:... Add a firewall rule first — inbound connections are denied until a rule allows them. If your own network has no IPv6, use a public IPv4 or the VM's in-browser console.
IPv6 internet access
VM → networking → Internet access has an IPv6 internet switch. Turning it off blocks internet traffic on the VM's /64 in both directions. The VM keeps its addresses, and private connectivity inside its VPC is unaffected.
Firewall
The same firewall covers
IPv4 and IPv6. Rules can target IPv4, IPv6, or both, and accept IPv6
CIDRs such as 2001:db8::/32.
Private-only VMs
Choosing private only at create gives a VM no public IPv4 or IPv6. It's reachable only inside its VPC, and still reaches the internet through NAT for package installs and updates.
What's next
- Public IPs — dedicated IPv4 addresses.
- Firewall rules — inbound and outbound policy.
- VPCs & subnets — private connectivity.