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 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.
]]>You can use Private Service Connect backends to access published services. For more information, see About Private Service Connect backends.
]]>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.
]]>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.
]]>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.
]]>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 Connection mode.
]]>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:
For more information, see Internal ranges overview.
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 Preview.
]]>If you're a service producer that makes a service available through VPC Network Peering, you can migrate your service to Private Service Connect without changing the IPv4 address that consumers use to access the service. This feature is available in General Availability.
]]>Support for the following is available in General availability for dual-stack configurations:
next-hop-ilb) next-hop-address) For more information, see Next hops and features in the static routes overview.
]]>The following features of internal ranges are available in Preview:
For more information, see Internal ranges overview.
You can exclude IP address ranges from internal range automatic IP address allocation. This feature is available in Preview. For more information, see Reserve internal ranges.
You can create internal ranges that overlap with routes and subnets. This feature is available in General Availability. For more information, see Internal ranges overview.
]]>The following Private Service Connect monitoring metrics are available for both producers and consumers in General Availability:
Additionally, the NAT IP address capacity metric is available for producers in General Availability.
You can use these metrics to help monitor and troubleshoot published services, endpoints that connect to published services, and backends that connect to published services. For more information, see Monitor Private Service Connect connections.
]]>There is a known issue with global access endpoints that access services that are published by using internal passthrough Network Load Balancers or internal protocol forwarding (target instances). Private Service Connect doesn't validate that the global access setting on the endpoint matches the setting on the producer's load balancer. We recommend the following:
If you're a service consumer, only enable global access on an endpoint if you know that the producer's load balancer is configured for global access. For more information, see endpoint Known issues.
If you're a service producer whose services are hosted on internal passthrough Network Load Balancers or internal protocol forwarding (target instances), and those services are accessed through global access endpoints, ensure that global access is enabled on your services' load balancers. For more information, see published services Known issues.
VPC Flow Logs metadata annotations include InstanceGroupDetails. This feature is available in General Availability.
]]>You can create an internal range with the usage type FOR_MIGRATION to migrate a CIDR range from one subnet to another. For more information, see Migrating subnet ranges. This feature is available in General Availability.
IPv6-only subnets and instances are available in Preview. For more information, see the following:
For information about which services support IPv6-only configurations, see IPv6 support in Google Cloud.
]]>Private Service Connect port mapping is available in General Availability. Port mapping lets consumer virtual machine (VM) instances privately communicate with specific service ports on specific producer VMs through a single Private Service Connect endpoint.
]]>Support for IPv6 static routes with a next hop internal passthrough Network Load Balancer (next-hop-ilb) is available in Preview.
VPC Flow Logs includes the following metadata annotations in General Availability:
src_gateway and dest_gatewaysrc_google_service and dest_google_serviceload_balancingnetwork_servicepscFor more information, see Record Format.
]]>The following producer load balancers now support all Private Service Connect monitoring metrics:
In the Google Cloud Console, the Effective routes tab on the Routes page shows only routes that are effective. You can optionally show suppressed routes by using the Show suppressed routes toggle. You can also view the reason why a given route is suppressed. For more information, see List routes for a VPC network.
]]>