Hybrid Subnets is available in General Availability. Hybrid subnet routing lets a VPC network share a CIDR block with a connected on-premises network. This configuration helps you migrate workloads to Google Cloud without needing to change any IP addresses. During migration, workloads that have migrated to your VPC network can communicate with those remaining in the on-premises network by using internal IP addresses. After all workloads have migrated, you can disable hybrid subnet routing to restore normal routing behavior.
]]>Service producers can accept or reject connections from individual Private Service Connect endpoints. This feature is available in General Availability.
]]>You can update a service attachment's target service without recreating the service attachment. Consumer connections are preserved during the update, but traffic is briefly disrupted. This feature is available in General Availability.
For more information, including a list of supported configurations, see Service mutability.
]]>You can create Compute Engine instances that have multiple network interfaces in the same VPC network. This feature is available in Preview. For more information, see Multiple network interfaces in the same VPC network.
]]>You can use constraints in custom organization policies to provide more granular and customizable control over specific fields for internal ranges. For more information, see Manage VPC resources by using custom organization policies.
]]>You can bring your own IPv6 global unicast addresses (GUAs) to assign to a subnet's internal IPv6 address range. Although GUAs are typically public addresses, in this configuration they are used privately and function in the same way as Google Cloud-provisioned ULAs.
For more information, see Bring your own IP addresses.
]]>You can create individual static external IPv4 addresses from bring your own IP addresses (BYOIP) prefixes. This feature is available in General Availability and only applies to IPv4 regional v2 prefixes that are created after December 13, 2025.
For more information, see Enhanced IP address allocation.
]]>For auto mode VPC networks, added a new subnet 10.232.0.0/20 for the Bangkok
asia-southeast3 region. For more information, see
Global locations
and Auto mode IP ranges.
Dynamic Private Service Connect interfaces are available in General Availability. Private Service Connect interfaces let service producers initiate connections to service consumers. You can update a VM instance to add or remove dynamic Private Service Connect interfaces without needing to restart or recreate the instance.
For more information, see Private Service Connect interface types.
]]>Service producers can accept or reject connections from individual Private Service Connect endpoints. This feature is available in Preview.
]]>VPC Network Peering supports peering connections in consensus mode. This feature is available in General Availability. For more information, see Connection mode.
]]>Dynamic Network Interfaces (NICs) are available in General Availability.
Dynamic NICs let you update an instance to add or remove network interfaces without having to restart or recreate the instance.
You can also use Dynamic NICs when you need more network interfaces. The maximum number of vNICs for most machine types in Google Cloud is 10; however, you can configure up to 16 total interfaces by using Dynamic NICs.
For more information, see the following:
]]>You can specify a /96 IPv6 address range when reserving static regional IPv6
addresses. For more information, see the following:
This feature is available in General Availability.
]]>You can view IP address utilization when you list or describe subnets. IP address utilization displays the number of free and allocated IP addresses in a subnet. This feature is available in General Availability.
]]>VPC Flow Logs supports logging for Cloud Run resources that are configured with Direct VPC egress. This feature is available in General Availability.
For more information, see Serverless flows and ServerlessDetails field format.
]]>Private Service Connect health is available in Preview.
Private Service Connect health lets service producers define health states to support automatic cross-region failover for consumers that use Private Service Connect backends. For more information, see About Private Service Connect health for automatic cross-region failover.
]]>The following features of VPC Flow Logs are available in General Availability:
For more information, see About VPC Flow Logs records.
]]>The following features of VPC Flow Logs are available in General Availability through the Network Management API:
For more information, see Supported configurations.
]]>Service producers can publish services that are hosted on cross-region internal Application Load Balancers. This feature is available in General Availability. For more information, see Publish services by using Private Service Connect.
]]>You can create a VPC network that supports RDMA over Falcon transport, which lets you run AI and high performance computing (HPC) workloads on VM instances that have the IRDMA network interface type in Google Cloud, such as H4D instances. This feature is available in Preview. For more information, see RDMA network profiles.
IPv6-only subnets and instances are available in General Availability. For more information, see the following:
You can also use an IPv6-only NAT subnet to publish a service with Private Service Connect.
For information about which services support IPv6-only configurations, see IPv6 support in Google Cloud.
VPC Flow Logs supports logging for RDMA flows over Converged Ethernet, such as GPU-to-GPU flows from A3 Ultra, A4, and A4X VMs. This feature is available in General Availability. For more information, see About VPC Flow Logs records.
]]>VPC Flow Logs includes metadata annotations for Google services such as Google APIs and VPC-hosted services. The following annotations are available in General Availability:
service_nameconnectivityprivate_domainThese annotations are supported for flows between VMs in VPC networks and Google services and for flows between on-premises endpoints and Google services (through Cloud Interconnect and Cloud VPN). For more information, see GoogleServiceDetails field format.
]]>When you reserve an internal range with an automatically allocated IPv4 CIDR block, you can specify the allocation strategy that is used to select a free block. This feature is available in General Availability.
]]>VPC Network Peering supports peering connections in consensus mode. This feature is available in Preview. For more information, see Update strategy.
Dynamic Private Service Connect interfaces are available in Preview. You can update VM instances to add or remove dynamic Private Service Connect interfaces without restarting or recreating the instance.
For more information, see Private Service Connect interface types.
]]>The following features of policy-based routes are available in General Availability:
For more information, see Create policy-based routes.
]]>Private Service Connect service connectivity automation periodically retries endpoint create or delete operations that fail due to errors. This feature is available in General Availability. For more information, see Automatic retries for endpoint failures.
]]>The following features of VPC Flow Logs are available in Preview through the Network Management API:
For more information, see Supported configurations.
]]>VPC Flow Logs annotates RDMA traffic that is reported from A3 Mega VMs. This feature is available in General Availability. For more information, see About VPC Flow Logs records.
]]>Dynamic Network Interfaces (NICs) are available in Preview.
Dynamic NICs let you update an instance to add or remove network interfaces without having to restart or recreate the instance.
You can also use Dynamic NICs when you need more network interfaces. The maximum number of vNICs for most machine types in Google Cloud is 10; however, you can configure up to 16 total interfaces by using Dynamic NICs.
For more information, see the following:
]]>You can publish a Secure Web Proxy instance as a Private Service Connect service. Making Secure Web Proxy available as a published service lets you centralize egress traffic management across multiple VPC networks. This feature is available in General Availability.
]]>