The following sections describe quotas and limits for Cloud Interconnect. To change a quota, request additional quota by using the Google Cloud Console. Limits cannot generally be increased unless specifically noted.
This table highlights important quotas for each project. See the Cloud Console Quotas page for other quotas.
|Interconnects||Quota||This is the number of interconnects per project. Interconnects are not associated with regions or VPC networks.|
|Interconnect bandwidth per project||Calculated automatically||This quota represents the total interconnect bandwidth for the project,
calculated by adding up the bandwidths of each interconnect it contains.
The bandwidth of each interconnect is calculated by multiplying the capacities of its circuits (either 10 Gbps or 100Gbps) by the number of circuits in the interconnect. For example, an interconnect consisting of four 10 Gbps circuits has 40 Gbps of bandwidth. If you have two such interconnects in your project, this quota is automatically set to 80 Gbps.
|Interconnect attachments||Quota||This quota represents the number of interconnect attachments (VLANs) that you can configure in each region for your project. Regardless of this quota, you are also limited to a total of 16 interconnect attachments per interconnect. If you require additional attachments per interconnect, refer to Maximum number of interconnect attachments (VLANs) that can be associated with a single interconnect in limits, below.|
|Interconnect attachments total Mbps||Quota||This quota represents the maximum bandwidth capacity of all interconnect attachments in a given region for a given project, irrespective of their relationship with interconnects. In addition to this quota, the limits described in the next table apply.|
|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.|
The following limits apply to interconnects and interconnect attachments. Unless otherwise stated, these limits cannot be increased.
|Maximum number of physical circuits per interconnect||8 x 10 Gbps (80 Gbps) circuits or
2 x 100 Gbps (200 Gbps) circuits
|An interconnect 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 interconnect attachments (VLANs) that can be associated with a single interconnect||16||Each interconnect supports no more than 16 interconnect attachments (VLANs), even if you would otherwise have quota to create more interconnect attachments.|
|Maximum bandwidth per interconnect attachment||Capacities from 50 Mbps to 50 Gbps||The maximum possible bandwidth per interconnect attachment depends
on the bandwidth capacity you order. See the
for capacities. For Partner Interconnect, not all
partners offer all capacities.
The throughput of individual flows on an interconnect attachment is limited, as described below. To achieve maximum throughput, you must use multiple five-tuple flows (for example: 10+) with packet sizes within the MTU of the interconnect attachment.
|Maximum total packet rate per interconnect attachment (VLAN)||This rate varies according to the attachment's
||This represents the maximum packet rate for the entire interconnect attachment (VLAN).|
|Maximum bandwidth per traffic flow on an interconnect attachment||3 Gbps. Even if you configure your attachment above 3 Gbps, your per-flow capacity is capped at 3 Gbps.||A traffic flow is identified by either a five-tuple hash for non-fragmented
packets or a three-tuple hash for fragmented packets.
|Maximum packet rate per traffic flow on an interconnect attachment||250,000 packets per second||This number represents the maximum rate of packets per traffic flow, as 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||1440 bytes||The size of the largest IP packet that can be transmitted over an interconnect attachment.|
|Maximum lifetime of (Partner) interconnect attachment pairing key||28 days||The maximum amount of time that can pass between generating a (partner) interconnect attachment pairing key and successful attachment provisioning by the partner. If a pairing key is no longer valid, you just delete and recreate a new pairing key for the partner interconnect provider to use.|
|Cloud Router limits||Because Dedicated Interconnect and Partner Interconnect require Cloud Router, all of 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. Carefully review the Cloud Router Quotas and limits page for more information.|
Cloud Interconnect enforces quotas on resource usage for a variety of 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) members need one of the following roles.
|Check quotas for a project||Project Owner or Editor or Quota Viewer|
|Modify quotas, request additional quota||Project
Owner or Editor,
or custom role with the
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
Request additional quota from the Quotas page in the Cloud Console. Quota requests take 24 to 48 hours to process.
- 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.
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 a 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 service level agreement (SLA) for the type of resource. For more information, review the relevant SLA for the resource.