VPC networks, including their associated routes and firewall rules, are global resources
Subnets are regional resources.
Network can span multiple regions
Subnets can spanm multiple zones
All GCP networking resources are assigned to a VPC network
Subnets can be converted from automatic to custom but not the otherway
Instances in a VPC network can communicate with Google APIs and services using private IP addresses if you enable private Google access for them.
You can share a VPC network from one project to instances in another project within the same organization using shared VPC. Shared VPC enables multi-tenancy deployments and delegated instance administration while separately maintaining network administrative controls.
VPC networks can be connected to other GCP VPC networks from different projects or organizations by using VPC peering.
VPC networks can be securely connected in hybrid environments by using VPN connections or dedicated interconnect.
VPC administration can be secured using Identity and Access Management (IAM) roles
Resources within a VPC network can communicate with one another using internal (private) IPv4 addresses, subject to applicable network firewall rules