Skip to content

VPC FAQ

View as Markdown

I created a VPC but cannot reserve an IP in it. Why?

Section titled “I created a VPC but cannot reserve an IP in it. Why?”

A VPC you create under Networking > VPC is for virtual machines on a CPU plan. A reserved IP of Type Private, also called a VPC IP, comes from a VPC in your E2E MyAccount project. See VPCs and Reserved IPs.

Virtual machines on a CPU plan in Delhi and Chennai can use a VPC. To give a GPU instance or an inference service a private address, reserve an IP of Type Private from a VPC in your E2E MyAccount project. See VPCs and Reserved IPs.

No. A VPC belongs to one project in one region. See VPCs.

No. You set the range when you create the VPC, and after that you can change only the name. If you need a larger range, create a new VPC with one. See VPC address ranges.

Your account can have five VPCs in each region, counted across all its projects. Support can raise the limit. See VPCs.

Yes. Attaching, switching, or detaching a VPC restarts the VM, so save your work first. A VM holds one VPC at a time. See Attach a VPC to a VM.

No. A VPC belongs to one project in one region. Create a VPC in each project that needs one.

Yes. Each VPC is a network of its own, and its traffic stays apart from every other VPC, even one with the same range.

No. Use a range inside 172.16.0.0 to 172.29.255.255 or inside 192.168.0.0/16. A VPC refuses 10.0.0.0/8, 172.30.0.0/16, and 172.31.0.0/16. See VPC address ranges.

Why does my VPC have nine fewer addresses than its range?

Section titled “Why does my VPC have nine fewer addresses than its range?”

Every VPC sets aside its first eight addresses and its last one for networking. A /24 gives 247 addresses to your machines. See Reserved addresses.

No. Every project has a default VPC that TIR manages and keeps off the list, so the name default is reserved in any mix of upper and lower case.

A VPC is free. See VPCs.