This document lists the quotas and limits that apply to Cloud Router.
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 covers important quotas per project. For other quotas, see the Cloud Console Quotas page.
|Cloud Routers per project||Quota||Regardless of quota, each network is limited to five Cloud Routers per region. See Limits.|
The following limits for Cloud Router apply to Virtual Private Cloud (VPC) networks. Unless otherwise stated, these limits cannot be increased.
|Maximum number of Cloud Routers per combination of VPC network and 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 given VPC network and 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 of 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 destination limits without reaching the other. When either of the limits has been reached, you can experience intermittent connectivity issues when the routes are dropped. For details, see the learned route example.
For more information about these limits, including metrics that you can use to understand your current limits and usage, see Check quotas and limits in Troubleshooting.
If you need to increase either of these limits, contact your Google Cloud sales team.
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 examples illustrate the route dropping behavior that you can encounter when the regional or global limit is exceeded.
Suppose you have Cloud Routers in the
us-east1 region and
Cloud Routers in the
us-west1 region in the same VPC network, and
global dynamic routing is enabled. The Cloud Routers in each region
learn a set of routes for 100 unique destinations. For the purpose of this
example, the Cloud Routers in each region don’t learn any of the same
Regardless of which Cloud Routers learn the routes within each region, each region’s regional limit is exhausted because 100 of 100 unique destinations are learned by the Cloud Routers in each region. The global limits for both regions are exhausted because the Cloud Routers in each region import 100 unique destinations from the Cloud Routers in the other region. If the example VPC network used regional dynamic routing, the global limits in each region would not apply because the regional dynamic routing mode does not propagate learned custom dynamic routes from one region to another.
Exceeding a region’s regional limit
Suppose your on-premises router that's connected to a Cloud Router in
us-west1 advertises a new route with a 101 destination. Cloud Routers in
us-west1 region pick the routes for 100 of the 101 unique destinations
following a deterministic order. The routes that use these selected (100 unique)
destinations are made available to resources in the
us-west1 region. Those
same routes are made available to other regions, subject to each other region’s
Exceeding a region’s global limit
When 101 unique destinations are learned by Cloud Routers in the
us-west1 region, routes for 100 of those 101 unique destinations from
are made available to resources in the
us-east1 region, because the
region’s global limit can only accept 100 unique destinations.
Suppose that you create a Cloud Router in a third region,
the same VPC network. Suppose that the new Cloud Router learns 10 unique
destinations from its BGP peer. Although the
us-central1 region’s regional
destination limit has not been exceeded, the
us-central1 region’s global
unique destination limit has been exceeded because a total of 200 unique
destinations are provided by the other two regions (100 from
us-east1 and a
different 100 from
us-west1). In each region, the deterministic route order
selects routes for no more than 100 unique destinations from other regions, as
indicated in the following table.
Unique destinations local to the region
(usage of region’s regional limit)
Unique destinations from other regions
(usage of region’s global limit)
|us-west1||101 received. 100 of the 101 are considered according to the deterministic route dropping. Only the 100 selected prefixes are advertised to remote regions.||
110 received (100 from
|us-east1||100 received. All 100 are considered and advertised to remote regions.||
110 received (100 from
|us-central1||10 received. All 10 are considered.||
200 received (100 from
us-central1 region’s global limit is exceeded, its regional quota can accept routes whose next hops are in the
Deterministic route dropping behavior
Cloud Router implements a deterministic route dropping behavior so that, as long as the same prefixes are received in each region, a consistent set of routes are made available to resources within that region. This consistency is preserved when Cloud Router tasks restart. If a limit is exceeded, Cloud Router drops prefixes according to a predictable algorithm regardless of when the routes were learned or the MED values of these routes. A new route can cause a previously learned route to be dropped by the algorithm.
As shown in exceeding a region’s global limit, the deterministic dropping behavior is applied independently to each region’s regional limit and each region’s global limit. The set of 100 unique prefixes that are not dropped in each region due to reaching each region’s global limit (the last column) is not guaranteed to be the same.
Avoiding route dropping
During route dropping, you lose connectivity for the prefixes that are dropped. To avoid route dropping, monitor each region’s regional and global prefix usage by using Cloud Monitoring or Cloud Logging, and make sure not to advertise more unique destinations than each limit.
Consider aggregating prefixes (for example, by aggregating prefixes into a prefix of smaller length) to reduce the number of unique destinations. If aggregating prefixes isn’t possible, contact your Google Cloud Sales team to discuss alternative options.
由於各方面因素的考量，Cloud Router 對資源用量實施配額限制。舉例來說，限制配額可以預防用量突然暴增的情況，進而保障 Google Cloud 使用者社群的權益。採用Google Cloud免費方案探索的使用者也能透過配額，確保不會超出試用範圍。
如要查看配額或要求增加配額，身分與存取權管理 (IAM) 成員需具有下列其中一種角色。
- 在 Cloud Console 中，前往「配額」頁面。
- 使用篩選表格搜尋要更新的配額。 如果不知道配額名稱，請改用本頁面上的連結。
PROJECT_ID 替換為您的專案 ID。
gcloud compute project-info describe --project PROJECT_ID
gcloud compute regions describe example-region
quota exceeded 錯誤訊息並傳回結束代碼
一旦超出 API 要求的配額上限，Google Cloud 就會傳回下列 HTTP 狀態碼：
HTTP 413 Request Entity Too Large
您可以透過 Cloud Console 中的「配額」頁面申請更多配額。處理配額要求需要花費 24 至 48 小時。
- 在 Cloud Console 中，前往「配額」頁面。
- 按一下頁面頂端的 [編輯配額] 。
- 輸入您的姓名、電子郵件地址和電話號碼，然後按一下 [下一步]。
- 輸入您的配額要求，然後按一下 [完成]。
us-central1 區域中建立全新地區性外部 IP 位址，但如果該區域中沒有可用的外部 IP 位址，則無法建立。區域的資源可用性也會影響您建立新資源的能力。
整個區域的資源皆無法提供使用的狀況很罕見。然而，可用區內的資源有時可能會耗盡，不過一般來說並不會對該資源類型的服務水準協議 (SLA) 造成影響。如需更多資訊，請參閱與該資源相關的 SLA。