Quotas and limits

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.

Quotas

This table highlights important quotas for each project. For other quotas, see the Cloud Console Quotas page.

Item Quota Notes
Interconnect connections Quota

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.

VLAN attachments Quota

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.

Cloud Routers Quota

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.

Limits

The following limits apply to Interconnect connections and VLAN attachments. Unless otherwise stated, these limits cannot be increased.

Item Limit Notes
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:

  • Up to 2 x 100 Gbps (200-Gbps) circuits.
  • 10-Gbps increments up to eight circuits (80 Gbps) to increase the maximum total bandwidth of all VLAN attachments that use the Interconnect connection to 80 Gbps.

    To determine the bandwidth, multiply the number of physical circuits by the bandwidth per circuit (10 Gbps).

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 rate for a 50-Gbps VLAN attachment is 6.25 M packets per second (pps).
  • The maximum rate for a 10-Gbps VLAN attachment is 1.25 M packets per second (pps).
The maximum packet rate for the entire VLAN attachment.
Maximum bandwidth per traffic flow on a VLAN attachment

3 Gbps

Even if you configure your attachment higher than 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:

  • A five-tuple hash consists of a protocol, source IP address, source port, destination IP address, and destination port.
  • A three-tuple hash consists of a protocol, source IP address, and destination IP address.

The following cases describe where the maximum bandwidth is lower than 3 Gbps:

  • If the bandwidth capacity of your VLAN attachment is less than 3 Gbps, the bandwidth per traffic flow is limited by the bandwidth of the VLAN attachment.
  • If you reach the maximum packet rate per traffic flow (as described in the next section).
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 對資源用量實施配額限制。舉例來說,限制配額可以預防用量突然暴增的情況,進而保障 Google Cloud 使用者社群的權益。採用Google Cloud免費方案探索的使用者也能透過配額,確保不會超出試用範圍。

所有專案最初的配額均相同,您可以要求額外配額來變更配額數量。某些配額可能會依據您使用產品的狀況而自動增加。

權限

如要查看配額或要求增加配額,身分與存取權管理 (IAM) 成員需具有下列其中一種角色。

工作 必要角色
查看專案的配額 專案擁有者或編輯者「或」配額檢視者
修改配額,要求額外配額 專案擁有者或編輯者配額管理員或具有 serviceusage.quotas.update 權限的自訂角色

查看配額

主控台

  1. 在 Cloud Console 中,前往「配額」頁面。

    前往配額頁面

  2. 使用篩選表格搜尋要更新的配額。 如果不知道配額名稱,請改用本頁面上的連結。

gcloud

如果您使用 gcloud 指令列工具,請執行下列指令來查看配額。請將 PROJECT_ID 替換為您的專案 ID。

      gcloud compute project-info describe --project PROJECT_ID

如要查看特定區域的配額用量,請執行下列指令:

      gcloud compute regions describe example-region

超出配額時產生錯誤

一旦超出 gcloud 指令的配額上限,gcloud 就會輸出 quota exceeded 錯誤訊息並傳回結束代碼 1

一旦超出 API 要求的配額上限,Google Cloud 就會傳回下列 HTTP 狀態碼:HTTP 413 Request Entity Too Large

申請更多配額

您可以透過 Cloud Console 中的「配額」頁面申請更多配額。處理配額要求需要花費 24 至 48 小時。

主控台

  1. 在 Cloud Console 中,前往「配額」頁面。

    前往配額頁面

  2. 「配額」頁面中,選擇您要變更的配額項目。
  3. 按一下頁面頂端的 [編輯配額]
  4. 輸入您的姓名、電子郵件地址和電話號碼,然後按一下 [下一步]
  5. 輸入您的配額要求,然後按一下 [完成]
  6. 提交要求。

資源可用性

如果特定類型的資源可以使用,則每項配額代表您能針對該資源建立的最大數量。請特別留意,配額「並不」保證資源可用性。即使您有可用的配額,如果資源無法提供使用,您也無法建立新的資源。

舉例來說,您可能有足夠的配額在 us-central1 區域中建立全新地區性外部 IP 位址,但如果該區域中沒有可用的外部 IP 位址,則無法建立。區域的資源可用性也會影響您建立新資源的能力。

整個區域的資源皆無法提供使用的狀況很罕見。然而,可用區內的資源有時可能會耗盡,不過一般來說並不會對該資源類型的服務水準協議 (SLA) 造成影響。如需更多資訊,請參閱與該資源相關的 SLA。

What's next