Quotas and limits

The following sections describe quotas and limits for Cloud VPN. To change a quota, request additional quota by using the Google Cloud Console. Limits cannot generally be increased unless specifically noted.

Quotas

This table covers important quotas per project. For other quotas, see the Cloud Console Quotas page.

Item	Quota	Notes
VPN gateways	Quota	For HA VPN only
External VPN gateways	Quota	For HA VPN only
VPN tunnels	Quota	This quota represents the combined total number of Classic VPN tunnels and HA VPN tunnels.
Routers	Quota	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.
Target VPN gateways	Quota	For Classic VPN only
Forwarding rules	Quota	For Classic VPN only

Limits

The following limits apply to Cloud VPN. In this table, VPN tunnel means either a Classic VPN tunnel or an HA VPN tunnel. Unless otherwise stated, these limits cannot be increased.

Item	Limit	Notes
Bandwidth per VPN tunnel	Up to 3 Gbps for the sum of ingress and egress	This maximum bandwidth can only be achieved by using an MTU size of 1,460 bytes and a packet rate of 250,000 packets per second (pps). Cloud VPN only throttles egress IPsec traffic. It does not throttle ingress traffic. For more details, see Network bandwidth.

Item

Limit

Notes

Bandwidth per VPN tunnel

Up to 3 Gbps for the sum of ingress and egress

This maximum bandwidth can only be achieved by using an MTU size of 1,460 bytes and a packet rate of 250,000 packets per second (pps).

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

For more details, see Network bandwidth.

Known issues

Be aware of the following issues:

Google Cloud resources specific to HA VPN are not yet displayed in Cloud Asset Inventory or Security Command Center. These resources include compute.vpnGateways and compute.externalVpnGateways. However, the compute.vpnTunnels resource is listed in both locations and is required for a working HA VPN connection.
To view Cloud Monitoring metrics for HA VPN, use Metrics Explorer. For more information, see Viewing logs and metrics.
When setting up VPN tunnels to AWS, use IKEv2 and configure fewer IKE transform sets.

Managing quotas

Cloud VPN enforces quotas on resource usage for various 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.

Permissions

To view quotas or request quota increases, Identity and Access Management (IAM) members need one of the following roles.

Task	Required role
Check quotas for a project	One of the following: Project Owner role (`roles/owner`) Project Editor role (`roles/editor`) Quota Viewer role (`roles/servicemanagement.quotaViewer`)
Modify quotas, request additional quota	One of the following: Project Owner role (`roles/owner`) Project Editor role (`roles/editor`) Quota Administrator role (`roles/servicemanagement.quotaAdmin`) A custom role with the `serviceusage.quotas.update` permission

Checking your quota

Console

In the Cloud Console, go to the Quotas page.
Go to Quotas
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

Using the 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 command, gcloud outputs a quota exceeded error message and returns with the exit code 1.

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.

Console

In the Cloud Console, go to the Quotas page.
Go to Quotas
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.

Resource availability

Each quota represents a maximum number for a particular type of resource that you can create, if that resource is available. It's important to note that quotas do not guarantee resource availability. Even if you have available quota, you can't 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. However, that is not possible if there are 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.

What's next

To find quotas and limits information for other Network Connectivity products, see Network Connectivity quotas and limits.