Release Notes

This page contains release notes for features and updates to Google Cloud Platform VPC networking.

To get the latest product updates delivered to you, add the URL of this page to your feed reader.

April 09, 2019

Serverless VPC Access is now available in Beta.

April 05, 2019

You can get up to 32Gbps of network I/O for virtual machines that use either the Skylake CPU platform or ultramem machine types. This increased egress rate is now available in Beta.

April 04, 2019

VPC Flow Logs log volume reduction is now available in Beta.

April 01, 2019

For VPC Network Peering, importing and exporting custom routes is now available in Beta.

March 27, 2019

Private services access is now available in General Availability.

February 07, 2019

You can disable the default network creation for new projects. You must create an organization policy and add the compute.skipDefaultNetworkCreation constraint.

February 01, 2019

The private access option for on-premises hosts is now Generally Available. On-premises hosts with only private IP addresses can access Google APIs through a Cloud VPN or Cloud Interconnect connections (hybrid connectivity scenarios).

January 24, 2019

The IPv4Range field for creating legacy networks is now deprecated and will shut down on February 1, 2020.

January 09, 2019

Firewall rules logging is now available in General Availability.

December 20, 2018

IP address allocation for private services access is now available in General Availability.

October 19, 2018

Private Google Access for on-premises hosts is now available in Beta. On-premises hosts with only private IP addresses can now access Google APIs through Cloud VPN or Cloud Interconnect connections (hybrid connectivity scenarios).

September 26, 2018

Private services access provides a private connection between your VPC network and a network owned by Google or a third party. Private services access is in Beta.

September 18, 2018

Firewall rules logging is now available in Beta.

September 05, 2018

The ability to Disable firewall rules is now available in General Availability.

July 31, 2018

In Shared VPC service projects, listing usable subnets in the host project is now available in General Availability.

June 28, 2018

VPC Flow Logs are now available in General Availability.

May 09, 2018

Folder support for Shared VPC is now available in Beta.

May 01, 2018

The ability to Disable firewall rules is now available in Beta.

April 23, 2018

Add/Delete Alias IP Ranges is now available in General Availability.

March 29, 2018

VPC Flow Logs are now available in Beta.

November 13, 2017

VPC Networks documentation has moved to https://cloud.google.com/vpc/docs.

September 5, 2017

Alias IP Ranges allows you to assign additional IP addresses to a VM instance. These addresses can be used by containers running on the VM. Alias IP Ranges is now available in General Availability.

Firewall Rules egress and deny rules allows you to create firewall rules that govern egress as well as ingress traffic. You can now also create deny rules and you can prioritize the order in which rules are evaluated. Firewall Rules egress and deny rules is now available in General Availability.

August 18, 2017

Multiple Network Interfaces allows a VM instance to have more than one virtual network interfaces. Each interface must point to a different VPC network. Multiple Network Interfaces is now available in General Availability.

August 11, 2017

Add support for specifying a static internal IP to Beta. See Reserving a Static Internal IP Address for more information.

July 14, 2017

VPC Network Peering allows you to peer VPC networks, even networks in different organizations, so that the networks can communicate with each other using internal IP addresses. VPC Network Peering is now available in General Availability.

June 21, 2017

Multiple Network Interfaces allows a VM instance to have more than one virtual network interface. Each interface must point to a different VPC network. Multiple Network Interfaces is now available in Beta.

June 7, 2017

Shared VPC (Previously Cross-Project Networking (XPN)) is now available in General Availability.

May 22, 2017

Alias IP Ranges allows you to assign additional IP addresses to a VM instance. These addresses can be used by containers running on the VM. Alias IP Ranges is now available in Beta.

May 8, 2017

VPC Network Peering allows you to peer VPC networks, even networks in different organizations, so that the networks can communicate with each other using internal IP addresses. VPC Network Peering is now available in Beta.

May 04, 2017

Private Google Access allows Compute Engine VM instances to access Google APIs using an internal IP address only. Private Google Access is now available in General Availability.

May 01, 2017

Decoupled labels and tags so that creating either a label or a tag will not create the opposing resource. For example, creating a label will no longer create a tag and vice-versa. For more information, read Relationship between instance labels and network tags.

You can now find information about network tags in the VPC networking documentation.

April 17, 2017

Firewall Rules egress and deny rules allows you to create firewall rules that govern egress as well as ingress traffic. You can now also create deny rules and you can prioritize the order in which rules are evaluated. Firewall Rules egress and deny rules is now available in Beta.

March 09, 2017

Shared VPC allows you to share a VPC network with other GCP projects. Shared VPC is now available in Beta.

March 07, 2017

Private Google Access allows Compute Engine VM instances to access Google APIs using an internal IP address only. Private Google Access is now available in Beta.

December 21, 2016

Added ICMP support for forwarding rules.

May 11, 2016

The following VPC IAM roles are now generally available: roles/compute.networkAdmin, roles/compute.securityAdmin, roles/iam.serviceAccountActor

For more information, read the IAM documentation.

November 04, 2014

Lowered network pricing. See Network pricing for more information.

May 05, 2014

Updated default firewall rule names. Default firewall rules are automatically created with every project. These rules were previously named default-internal and default-ssh. New projects will have the same default firewalls but with the following new names:

  • default-allow-internal - Allows network connections of any protocol and port between any two instances.
  • default-allow-ssh - Allows TCP connections from any source to any instance on the network, over port 22.

Introduced new default firewall rule that will be created with each new project.

  • default-allow-icmp - Allows ICMP traffic from any source to any instance on the network.

December 17, 2013

Released new Protocol Forwarding feature. Forwarding rules allows you to forward traffic to a single virtual machine instance, using a target.instance. Protocol forwarding provides support for these additional features:

Added support for new Target Instance resources, which allows for non-NAT'ed traffic to be forwarded to a single virtual machine instance. See Forwarding rules for more information.

Was this page helpful? Let us know how we did:

Send feedback about...

Virtual Private Cloud
Need help? Visit our support page.