Quotas and limits

This quota represents 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.

Subject to the Cloud Router quotas and limits, the number of Cloud Routers is independent of the type of Cloud VPN gateway, Classic VPN or HA VPN, that a tunnel is attached to. The quota is applied the same to either type of gateway.

250,000 packets per second is roughly equivalent to 1 Gbps to 3 Gbps, depending on the average packet size within the tunnel.

Cloud VPN only throttles egress IPsec traffic. It does not throttle ingress traffic.

For more details, see Network bandwidth.

The number of Dedicated Interconnect connections per project.

Interconnect connections are not associated with regions or VPC networks.

The number of VLAN attachments that you can configure in each region for your project. This includes VLAN attachments for both Dedicated Interconnect and Partner Interconnect.

In addition to this quota, the VLAN attachments per Interconnect applies.

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.

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).

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.

Dataplane v1: 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).

• Dataplane v2: 10 Gbps
• Dataplane v1: 3 Gbps

Even if you configure your attachment with a higher bandwidth, an individual traffic flow might be limited to the maximum defined for the Dataplane version.

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.

• 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 the 3 Gbps or 10 Gbps limit:

• If the bandwidth capacity of your VLAN attachment is less than the maximum for its Dataplane version (3 Gbps or 10 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).

• Dataplane v2: 10,000,000 packets per second (pps)
• Dataplane v1: 250,000 packets per second

• 1,440 bytes
• 1,460 bytes
• 1,500 bytes
• 8,896 bytes

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.

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 routes and on the number of advertised routes. For more information, see the Cloud Router Quotas and limits page.

Unique Cloud Router dynamic route prefixes from own region per region per VPC network

The maximum number of assured unique destination prefixes for learned routes to be applied to subnets in a given region by all Cloud Routers in the same region. This is referred to as a region's from-own-region quota.

Both IPv4 and IPv6 prefixes count toward this quota.

All learned routes count toward this quota, including custom learned routes and BGP-received 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 unique dynamic route prefix quotas without reaching the other. If either of the quotas has been exceeded, you may experience intermittent connectivity issues when routes are dropped./ For details, see the learned route example.

For more information about these quotas, including metrics that you can use to understand your current usage, see Troubleshoot BGP routes and route selection.

Only applicable to VPC networks in global dynamic routing mode.

Unique Cloud Router dynamic route prefixes from other regions per region per VPC network

The maximum number of assured unique destinations for learned routes that can be applied to subnets in a given region by Cloud Routers from different regions. This is referred to as a region's from-other-regions quota.

Both IPv4 and IPv6 prefixes count toward this quota.

All learned routes count toward this quota, including custom learned routes and BGP-received 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 unique dynamic route prefix quotas without reaching the other. If either of the quotas has been reached, you might experience intermittent connectivity issues when routes are dropped. For details, see the learned route example.

For more information about these quotas, including metrics that you can use to understand your current usage, see Troubleshoot BGP routes and route selection.

• A Cloud VPN tunnel using dynamic routing
• A VLAN attachment for any of the following:
  • Dedicated Interconnect
  • Partner Interconnect
  • Cross-Cloud Interconnect
• A Router appliance within Network Connectivity Center

For more information about this feature, see Custom learned routes.

For a given region in a VPC network, the maximum number of unique IP prefixes that can be configured as custom learned routes; this limit allows for the same ranges to be used on multiple peers

For more information about this feature, see Custom learned routes.

251 received. 250 of the 251 are selected, and one of the 251 is dropped by the deterministic route order. 250 dynamic routes with next hops in us-west1 are created in us-west1.

The 250 selected prefixes are shared with other regions.

260 received (250 from us-east1, 10 from us-central1). 250 of the 260 are selected, and 10 of the 260 are dropped by the deterministic route order.

250 dynamic routes with next hops outside of us-west1 are created in us-west1.

250 received. All 250 are selected by the deterministic route order. 250 dynamic routes with next hops in us-east1 are created in us-east1.

All 250 selected prefixes are shared with other regions.

260 received (250 from us-west1, 10 from us-central1). 250 of the 260 are selected, and 10 of the 260 are dropped by the deterministic route order.

250 dynamic routes with next hops outside of us-east1 are created in us-east1.

10 received. All 10 are selected by the deterministic route order. 10 dynamic routes with next hops in us-central1 are created in us-central1.

All 10 selected prefixes are shared with other regions.

500 received (250 from us-west1, 250 from us-east1). 250 of the 500 are selected, and 250 of the 500 are dropped by the deterministic route order.

250 dynamic routes with next hops outside of us-central1 are created in us-central1.

Number of active VPC spokes per hub

Only applicable to VPC spokes that have been accepted into a hub; not applicable to VPC spokes that are pending review or that have been rejected.

Number of subnet routes per hub route table

• Project Owner (roles/owner)
• Project Editor (roles/editor)
• Quota Viewer (roles/servicemanagement.quotaViewer)

• Project Owner (roles/owner)
• Project Editor (roles/editor)
• Quota Administrator (roles/servicemanagement.quotaAdmin)
• A custom role with the serviceusage.quotas.update permission