VPC Resource Quotas

Quotas and limits

The following sections describe quotas and limits for VPC networks. To change a quota, simply request additional quota using the GCP Console. Limits cannot generally be increased unless specifically noted.

Per project

This table highlights important global quotas for each project. See the quotas page for other quotas.

Item Quota Notes
Networks Quotas This includes includes the default network, which you can remove.
Subnets Quotas Applies to all subnets in all networks in the project.
Allocated IP address ranges Quotas This quota represents the number of contiguous internal IP address ranges you can allocate for private services access. This quota applies to your project, not to particular VPC networks or regions.
System-generated and
custom static routes
Quotas This quota does not include custom dynamic routes learned by Cloud Router.
Cloud Routers Quotas This quota represents the number of Cloud Routers you can create within your project, in any network and region. Networks also have a limit on the number of Cloud Routers in any given region. See Cloud Router quotas and limits for more details.
Forwarding rules Quotas This quota includes all forwarding rules, regardless of their targets. Networks also have a limit on the total number of forwarding rules used with Internal Load Balancing. See Forwarding rules used with Internal Load Balancing per network below.

Shared VPC project limits

The following limits apply to projects that participate in Shared VPC.

Item Limit Notes
Number of service projects that can be attached to a host project 100 Contact your GCP sales team if you need to increase this limit.
Number of Shared VPC host projects 100 This limit cannot be increased.
Number of host projects to which a service project can attach 1 This limit cannot be increased.

Per network

The following limits apply to VPC networks. Unless otherwise noted, these limits can be increased if you contact your GCP sales team.

Item Limit Notes
VM instances per network 15,000 The number of instances per network may be reduced you connect the network to others using VPC Network Peering. See Total VM instances among peered networks for details.
VM instances per subnet No separate restriction.
Total VM instances among peered networks 15,500 This limit represents the total number of instances possible among all networks in a VPC Network Peering relationship.
As clarifying examples, suppose network B is peered with two other networks, A and C:
    • If network B has 5,000 instances, the total number of instances in both A and C together must be less than or equal to 10,500.
    • If network B has 500 instances, the total number of instances in both A and C together must be less than or equal to 15,000.
Alias IP ranges 15,000 An alias IP range can be a single IP address (/32) or a CIDR block of IP addresses, such as a /24 or /16.
For the purposes of this limit, GCP does not consider the size (netmask) of the alias range. Only the number of alias IP ranges assigned for all VMs in the network are counted.
Secondary (alias) IP ranges per subnet 5 This limit cannot be increased.
Maximum number of forwarding rules for Internal Load Balancing per network 50 This represents the maximum number of forwarding rules that can be used for Internal Load Balancing within a given network.
Maximum number of forwarding rules for Internal Load Balancing among peered networks 50 When VPC Network Peering is used with Internal Load Balancing, the total number of internal forwarding rules among all peer networks must not exceed this limit.
Number of VPC Network Peering connections 25 A network can have up to 25 directly peered networks in total. This total includes both active and inactive peerings.
Cloud Router limits For information about the total number of routers, BGP peers, custom route advertisements, and learned routes, see Cloud Router quotas and limits.

Per instance

The following limits apply to VM instances. They cannot be changed. See Compute Engine quotas for quotas relevant to VMs.

Item Limit Notes
Maximum Transmission Unit (MTU) 1,460 bytes Instances using larger MTU sizes can experience dropped packets. You cannot increase this MTU value.
Maximum number of network interfaces 8 Network interfaces are defined at instance creation time, and cannot be changed by editing the instance later.
Network interfaces per VPC network 1 Each network interface must be connected to a unique VPC network. An instance can only have one network interface in a given VPC network.
Maximum duration for idle TCP connections 10 minutes VPC networks automatically drop idle TCP connections after ten minutes. You cannot change this limit, but you can use TCP keepalives to prevent connections to instances from becoming idle. See the Compute Engine tips and troubleshooting page for details.
Maximum ingress data rate Depends on machine type GCP does not impose bandwidth caps for ingress traffic. The amount of traffic a VM can handle depends on its machine type and operating system. Ingress data rates are not affected by the number of network interfaces a VM has or any IP aliases it uses.
Maximum egress data rate 2 Gbps per vCPU
Up to 16 Gbps
GCP limits egress traffic to 2 Gbps per vCPU for machine types with eight or fewer vCPUs. Machine types with more than eight vCPUs are limited to 16 Gbps, and shared-core machine types are limited to 1 Gbps. Actual egress rates depend on other factors; refer to this page for more information. Egress rates include data transfer rates to persistent disks.


Virtual Private Cloud enforces quotas on resource usage for a variety of reasons. For example, quotas protect the community of Google Cloud Platform users by preventing unforeseen spikes in usage. Quotas also help users who are exploring GCP with the free tier to stay within their trial.

All projects start with the same quotas, which you can change by requesting additional quota. Some quotas may increase automatically, based on your use of a product.


To view quotas or request quota increases, IAM members need one of the following roles.

Task Required Role
Check quotas for a project Project owner or editor or Quota Viewer
Modify quotas, request additional quota Project owner or editor, Quota Admin, or custom role with the serviceusage.quotas.update permission

Checking your quota

In the GCP Console, go to the Quotas page.

Using the gcloud command-line tool, run the following command to check your quotas. Replace [PROJECT_ID] with your own project ID.

    gcloud compute project-info describe --project [PROJECT_ID]

To check your used quota in a region, run:

    gcloud compute regions describe example-region

Requesting additional quota

Request additional quota from the Quotas page in the GCP Console. Quota requests take 24 to 48 hours to process.

  1. Go to the Quotas page.

    Go to the Quotas page

  2. In the Quotas page, select the quotas you want to change.
  3. Click the Edit Quotas button at the top of the page.
  4. Fill out your name, email, and phone number and click Next.
  5. Fill in your quota request and click Next.
  6. Submit your request.

Resource availability

Each quota represents a maximum number for a particular type of resource that you can create, provided that resource is available. It's important to note that quotas do not guarantee resource availability. Even if you have available quota, you won't be able to create a new resource if it is not available. For example, you might have sufficient quota to create new regional, external IP address in the us-central1 region, but that would not be possible if there were no available external IP addresses in that region. Zonal resource availability can also affect your ability to create a new resource.

Situations where resources are unavailable in an entire region are rare; however, resources within a zone can be depleted from time to time, typically without impact to the SLA for the type of resource. For more information, review the relevant Service Level Agreement (SLA) for the resource.

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

Send feedback about...