This document lists the quotas and limits that apply to Cloud Interconnect.
To change a quota, see requesting additional quota.
A quota restricts how much of a particular shared Google Cloud resource your Cloud project can use, including hardware, software, and network components.
Quotas are part of a system that does the following:
- Monitors your use or consumption of Google Cloud products and services.
- Restricts your consumption of those resources for reasons including ensuring fairness and reducing spikes in usage.
- Maintains configurations that automatically enforce prescribed restrictions.
- Provides a means to make or request changes to the quota.
When a quota is exceeded, in most cases, the system immediately blocks access to the relevant Google resource, and the task that you're trying to perform fails. In most cases, quotas apply to each Cloud project and are shared across all applications and IP addresses that use that Cloud project.
Many products and services also have limits that are unrelated to the quota system. These are constraints, such as maximum file sizes or database schema limitations, which generally cannot be increased or decreased, unless otherwise stated.
This table highlights important quotas for each project. For other quotas, see the Cloud Console Quotas page.
The number of Interconnect connections per project.
Interconnect connections are not associated with regions or VPC networks.
|Interconnect connection bandwidth per project||Calculated automatically||
The total Interconnect connection bandwidth for the project, calculated by adding up the bandwidths of each connection it contains.
The bandwidth of each connection is calculated by multiplying the capacities of its circuits (either 10 Gbps or 100 Gbps) by the number of circuits in the connection.
For example, an Interconnect connection consisting of four 10-Gbps circuits has 40 Gbps of bandwidth. If you have two such connections in your project, this quota is automatically set to 80 Gbps.
The number of VLAN attachments that you can configure in each region for your project.
Regardless of this quota, you are also limited to a total of 16 VLAN attachments per Interconnect connection. If you require additional attachments per connection, see the Maximum number of VLAN attachments that can be associated with a single Interconnect connection in the Limits table.
|VLAN attachments total Mbps||Quota||
The maximum bandwidth capacity of all VLAN attachments in a given region for a given project, irrespective of their relationship with Interconnect connections.
In addition to this quota, the limits described in the Limits table apply.
The number of Cloud Routers that 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.
For more details, see Cloud Router quotas and limits.
The following limits apply to Interconnect connections and VLAN attachments. Unless otherwise stated, these limits cannot be increased.
|Maximum number of physical circuits per Interconnect connection||8 x 10 Gbps (80-Gbps) circuits or
2 x 100 Gbps (200-Gbps) circuits
An Interconnect connection is a logical connection to Google, made up of one or more physical circuits. You can request one of the following circuit choices:
|Maximum number of VLAN attachments that can be associated with a single Interconnect connection||16||Each Interconnect connection supports no more than 16 VLAN attachments, even if you would otherwise have quota to create more VLAN attachments.|
|Maximum bandwidth per VLAN attachment||Capacities from 50 Mbps to 50 Gbps||
The maximum possible bandwidth per VLAN attachment depends on the bandwidth capacity that you order. For capacities, see the Pricing page. For Partner Interconnect, not all service providers offer all capacities.
The throughput of individual flows on a VLAN attachment is limited. To achieve maximum throughput, you must use multiple five-tuple flows (for example: 10+) with packet sizes within the MTU of the VLAN attachment.
|Maximum total packet rate per VLAN attachment||
This rate varies according to the attachment's capacity:
|The maximum packet rate for the entire VLAN attachment.|
|Maximum bandwidth per traffic flow on a VLAN attachment||
Even if you configure your attachment higher than 3 Gbps, your per-flow capacity is capped at 3 Gbps.
A traffic flow to a destination in a VPC network is identified by either a five-tuple hash for non-fragmented packets or a three-tuple hash for fragmented packets. In addition, traffic flows that use Private Google Access for on-premises hosts are identified by a three-tuple hash.
The following cases describe where the maximum bandwidth is lower than 3 Gbps:
|Maximum packet rate per traffic flow on a VLAN attachment||250,000 packets per second||The maximum rate of packets per traffic flow, identified by a five-tuple hash for non-fragmented packets and by a three-tuple hash for fragmented packets (as described in the previous section).|
|Maximum transmission unit (MTU)||1440 or 1500 bytes||Depending on the VLAN attachment MTU setting, the size of the largest IP address packet that can be transmitted over a VLAN attachment. For more information, see the Cloud Interconnect MTU section.|
|Maximum lifetime of (Partner Interconnect) VLAN attachment pairing key||28 days||
The maximum amount of time that can pass between generating a (Partner Interconnect) VLAN attachment pairing key and successful attachment provisioning by the service provider.
If a pairing key is no longer valid, you delete and create a new pairing key for the Partner Interconnect service provider to use.
|Cloud Router limits||
Because Dedicated Interconnect and Partner Interconnect require Cloud Router, all the Cloud Router quotas and limits apply.
There are limits on the maximum number of learned custom dynamic routes and on the number of advertised routes. For more information, see the Cloud Router Quotas and limits page.
Cloud Interconnect enforces quotas on resource usage for various reasons. For example, quotas protect the community of Google Cloud users by preventing unforeseen spikes in usage. Quotas also help users who are exploring Google Cloud 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, Identity and Access Management (IAM) principals need one of the following roles.
|Check quotas for a project||One of the following:|
|Modify quotas, request additional quota||One of the following:|
Checking your quota
- In the Cloud Console, go to the Quotas page.
- To search for the quota that you want to update, use the Filter table. If you don't know the name of the quota, use the links on this page instead.
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 the following command:
gcloud compute regions describe example-region
Errors when exceeding your quota
If you exceed a quota with a
gcloud outputs a
quota exceeded error
message and returns with the exit code
If you exceed a quota with an API request, Google Cloud returns the
following HTTP status code:
HTTP 413 Request Entity Too Large.
Requesting additional quota
To increase or decrease most quotas, use the Google Cloud Console. Some quotas can't be increased above their default values.
For more information, see the following sections of Working with quotas:
- In the Cloud Console, go to the Quotas page.
- On the Quotas page, select the quotas that you want to change.
- At the top of the page, click Edit quotas.
- Fill out your name, email, and phone number, and then click Next.
- Fill in your quota request, and then click Done.
- Submit your request. Quota requests take 24 to 48 hours to process.
Each quota represents a maximum number for a particular type of resource that you can create, if that resource is available. It's important to note that quotas do not guarantee resource availability. Even if you have available quota, you can't create a new resource if it is not available.
For example, you might have sufficient quota to create a new regional, external IP address
us-central1 region. However, that is not possible if there are 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 service level agreement (SLA) for the type of resource. For more information, review the relevant SLA for the resource.
- To find quotas and limits information for other Network Connectivity products, see Network Connectivity quotas and limits.