Quotas and limits
The following sections describe quotas and limits for Cloud Router. To change a quota, simply request additional quota using the Cloud Console.
|Cloud Routers per project||Quotas||Regardless of quota, each network is limited to five Cloud Routers per region. See limits below.|
The following limits for Cloud Router apply to VPC networks. Unless otherwise stated, these limits cannot be increased.
|Maximum number of Cloud Routers in a region||5||If you have sufficient project quota, you can create up to five Cloud Routers in a given VPC network and region.|
|Maximum number of BGP peers for each Cloud Router in a region||128||The BGP peer can be a Cloud VPN tunnel using dynamic routing or a VLAN attachment for Dedicated Interconnect or Partner Interconnect.|
|For a given Cloud Router, maximum number of subnet route advertisements per BGP session||No restriction||Cloud Routers do not have a limit for the number of subnet routes they can advertise. The number of subnet routes are determined by the number subnets, which are controlled by VPC network quotas and limits.|
|For a given Cloud Router, maximum number of custom route advertisements per BGP session||200||If the custom route advertisements are identical for all BGP sessions on a Cloud Router, this limit represents the total number of unique custom route advertisements for the Cloud Router. In this case, each session receives the same set of custom route advertisements.|
|Maximum number of unique destinations for learned routes that can be applied to subnets in a given region by all Cloud Routers in the same region||100||For both limits on the maximum number of unique destinations
for learned routes: Routes are grouped by unique destinations. Routes with
identical destinations but different next hops only count as a single
destination. Routes with identical destinations and identical next hops also
only count as a single destination.
For networks in global dynamic routing mode: It is possible to reach one of the maximum number of unique destinations for learned routes limits without reaching the other. When only one limit has been reached, you can experience unpredictable routing behavior. See the learned route example for details.
Contact your Google Cloud sales team if you need to increase either of these limits on the maximum number of learned routes.
|Only applicable to
VPC networks in global dynamic routing mode:
Maximum number of unique destinations for learned routes that can be applied to subnets in a given region by Cloud Routers from different regions
Learned route example
The following example illustrates unpredictable behavior you can encounter when only one of the limits for maximum number of learned routes is reached.
Suppose you have a Cloud Router in the us-east1 region and another in the us-west1 region. Both Cloud Routers learn the same set of routes for 100 unique destinations (to your on-premises network). The next hops for these routes are specific to each Cloud Router because each one connects to a different router at your on-premises network. If your on-premises router connected to the Cloud Router in us-west1 shares a 101st route with a new, unique destination:
The Cloud Router would pick any 100 of the 101 shared routes. Simultaneously, the limit for the number of unique destinations learned by Cloud Routers in different regions would be reached in us-east1, so a set of any 100 of those 101 routes would be applied to subnets in us-east1. There is no guarantee that the same 100 routes would be applied in both regions.
VMs in one region can experience loss of other routes. Suppose a route with destination
10.1.2.0/24is shared from on-premises to Cloud Routers in both regions. If us-east1 has reached the maximum number of unique destinations for learned routes, the other route with destination
10.1.2.0/24and next hop in us-west1 cannot be made available to subnets in us-east1. Subnets in us-east1 would not have a path to
More generally, if a Cloud Router in a given region and Cloud Routers in different regions both learn routes with the same destination (but different next hops), reaching the maximum number of unique destinations for learned routes in the given region causes Google Cloud to ignore routes with that destination whose next hops are on Cloud Routers in the other regions.
Cloud Router 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, 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.
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
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.
- Go to the Quotas page.
- In the Quotas page, select the quotas you want to change.
- Click the Edit Quotas button at the top of the page.
- Fill out your name, email, and phone number and click Next.
- Fill in your quota request and click Next.
- 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 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.