Understand connectivity changes when detaching instances from a Vultr VPC.
Removing an instance from a VPC changes how it connects to the network, and the outcome depends on whether the instance is VPC-only or publicly addressable.
If you remove a VPC-only instance from its VPC, the instance immediately loses all network connectivity.
The private IP address assigned from the VPC subnet is released, and the instance is no longer connected to any virtual network. As a result, it cannot communicate with other instances, access the internet through a NAT Gateway, or receive inbound traffic through port forwarding. Any services running on the instance become unreachable at the network level.
The instance remains powered on and retains its disk data, but it is effectively isolated until it is reattached to a VPC or redeployed with a valid network configuration. When the instance is attached to a VPC again, a new private IP address is assigned and connectivity is restored.
If the instance has a public IP assigned, removing it from the VPC releases the private IP but does not fully isolate the instance.
In this case:
This lets the instance remain externally accessible, but without any private network connectivity until it is attached to a VPC again.