VPC release notes

Preview: You can create v2 IPv4 public advertised prefixes for bring your own IP addresses (BYOIP) that use Standard Tier IP addresses. For more information, see Network Service Tiers.

General Availability: You can use the Resolve subnet mask setting on a subnet to configure all attached Compute Engine instances with the same netmask as the subnet (instead of /32). Configuring larger instance netmasks lets compute instances discover the MAC addresses of other machines within the same subnet and directly communicate with them by using destination MAC addresses.

For more information, see Compute instance netmasks.

For Google Cloud resources that are registered as App Hub workloads or services, VPC Flow Logs records contain application-specific labels. For more information, see App Hub labels.

Preview: You can reserve static external IPv6 addresses from bring your own IP addresses (BYOIP) sub-prefixes that are in EXTERNAL_IPV6_FORWARDING_RULE_CREATION mode.

You can assign these addresses to forwarding rules for external passthrough Network Load Balancers and external protocol forwarding. You can also promote ephemeral IPv6 BYOIP addresses that are used by external forwarding rules to reserved static IP addresses.

For more information, see Create external forwarding rules.

General Availability: If a consumer VPC network uses an RDMA network profile for Falcon VPC networks, a single Compute Engine instance can connect to it by using multiple virtual Private Service Connect interfaces.

For more information, see Create VMs with Private Service Connect interfaces.

General Availability: You can cancel pending deletion requests for VPC Network Peering connections that are in consensus mode. For more information, see Cancel a deletion request.

General Availability: Service consumers can authorize Private Service Connect interfaces to connect to network attachments by adding service class IDs to a network attachment's accept list.

For more information, see Authorization policies.

Preview: RoCE VPC networks for VM instances support assigning alias IP ranges to MRDMA vNICs. For more information about these features, see the following:

• RDMA network profiles
• Alias IP ranges

General Availability: Composite Health for Private Service Connect, formerly known as Private Service Connect health, lets service producers define health criteria for published services, enabling automatic cross-region failover for consumers that access the service by using Private Service Connect backends.

You can cancel pending deletion requests for VPC Network Peering connections that are in consensus mode. This feature is available in Preview. For more information, see Cancel a deletion request.

Organization Policy Service custom constraints are available in General Availability for private services access connections. For more information, see Restrict private connections with organization policies.

Private Service Connect consumers can configure supported load balancers or regional Cloud Service Mesh to access published services through Private Service Connect endpoints. This feature is available in Preview.

For more information, see Published service backends.

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.

For information about pricing for Hybrid Subnets, see Virtual Private Cloud pricing.

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 create a VPC network that supports RDMA over Falcon transport, which lets you run AI and high performance computing (HPC) workloads on Compute Engine instances that have the IRDMA network interface type in Google Cloud, such as H4D instances. This feature is available in General Availability.

For more information, see RDMA network profiles.

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:

• Dynamic NICs
• Create a VM instance with Dynamic NICs
• Add Dynamic NICs to an existing instance

You can specify a /96 IPv6 address range when reserving static regional IPv6 addresses. For more information, see the following:

• Reserve a static internal IP address
• Reserve a static external IP address

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:

• Logging for RDMA over Falcon transport
• Enhanced round-trip time precision for TCP and Falcon traffic

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:

• Enabling VPC Flow Logs for an organization
• Enabling VPC Flow Logs for a VPC network
• Enabling VPC Flow Logs for a subnet

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:

• Add an IPv6-only subnet
• Create an IPv6-only instance
• Configure IPv6-only subnets and instances with DNS64 and NAT64

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_name
• connectivity
• private_domain

These 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.

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.

VPC Network Peering supports peering connections in consensus mode. This feature is available in Preview. For more information, see Connection mode.

The following features of policy-based routes are available in General Availability:

• Applying policy-based routes to IPv6 traffic
• Using a next hop that is in a peered VPC network

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:

• Enabling VPC Flow Logs for an organization
• Enabling VPC Flow Logs for a VPC network
• Enabling VPC Flow Logs for a subnet

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:

• Dynamic NICs
• Create a VM instance with Dynamic NICs
• Add Dynamic NICs to an existing instance

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.

You can assign IPv6 bring your own IP (BYOIP) addresses to a subnet's external address range. These subnet ranges can only be used by VM instances, either as ephemeral or reserved addresses. To reserve addresses from these ranges, create a static regional external IPv6 address with the VM endpoint type. This feature is available in General Availability.

For more information, see Create and use IPv6 sub-prefixes.

Service producers can publish services that are hosted on cross-region internal Application Load Balancers. This feature is available in Preview. For more information, see Publish services by using Private Service Connect.

You can exclude IP address ranges from being used for automatic IP address allocation for internal ranges. This feature is available in General Availability. For more information, see Reserve internal ranges.

The following features of internal ranges are available in General Availability:

• Reserving internal ranges with IPv6 addresses
• Creating immutable ranges (ranges that can't be edited, except for the description)