VPC 2.0

Quake AI concept: Subnets

• Vultr exposes subnet settings as fields on the VPC resource rather than as a standalone subnet object. In the deprecated VPC 2.0 API, `POST /v2/vpc2` uses `ip_block` and `prefix_length`, and the network record itself returns those fields instead of a Neutron-style subnet collection. (Vultr API)
• VPC 2.0 is documented as deprecated, with Vultr directing users to VPC Networks instead of treating VPC 2.0 subnet handling as the current model. OpenStack Neutron subnets are still first-class API resources, but Vultr’s canonical docs frame the VPC 2.0 subnet model as legacy. (Vultr API, VPC Networks)
• A VPC 2.0 network is region-bound and cannot span regions, and Vultr says an instance can connect to multiple VPCs with a limit of up to 5 VPCs per region. That is a different resource model from OpenStack Neutron, where subnets are attached through networks and routers rather than being described as region-limited VPC memberships. (Vultr API)
• Vultr documents VPC 2.0 as a fully isolated network accessible only by instances on the account, and the API for changing the VPC itself only updates the description. There is no documented subnet CRUD flow for VPC 2.0, so subnet sizing is established at creation time rather than managed through a separate subnet lifecycle. (Vultr API)