Quota and limit definitions
A given quota or limit is calculated per resource. Quotas and limits may be per project, per network, per region, or per another resource. NAT IPs cannot be shared between NAT gateways.
|NAT gateways||50 per Cloud Router||Each network supports up to 5 Cloud Router instances per region, so you can have up to 250 Cloud NAT gateways per region per VPC network. For Cloud Router quotas, refer to the Cloud Router documentation|
|NAT IP addresses per gateway||50 manual addresses
300 auto-allocated addresses
|The maximum number of external IP addresses that you can have on a NAT gateway. However, regional restrictions also apply.|
|NAT IP addresses per region||300 auto-allocated addresses
12500 manually allocated addresses.
|The total number of manually allocated addresses is the product of (of routers per region) * (NAT gateways per router) * (IP addresses per NAT gateway)|
|Subnets ranges||50 per gateway||The maximum number of primary and secondary subnet IP address ranges that you can associate with a gateway.|
See the Cloud Router quotas page for quotas that affect Cloud NAT.
- Some servers such as legacy DNS servers require UDP port randomization among 64,000 ports for enhanced security. Since Cloud NAT selects a random port from one of 64 or user-configured number of ports, it is best to assign an external IP address to these servers instead of using Cloud NAT. Since Cloud NAT does not allow connections initiated from outside, most of these servers are required to use an external IP address anyway.
- Cloud NAT is not available for legacy networks.
- NAT ALGs (Application Level Gateway) functionality is not supported. This means that Cloud NAT does update IP in the packet data (such as for FTP, SIP, and other such protocols).
- VMs with an external IP address can have 64,000 TCP, 64,000 UDP, and 64,000 ICMP-query sessions (ping) simultaneously if they have enough compute/memory resources. For Cloud NAT, this limit is reduced to a total of 64,000 connections per VM for all supported protocols combined.
Small idle connection timeouts may not work.
NAT mappings are checked every 30s for expiration and configuration change. Even if a connection timeout value of 5s is used, the connection may not be available for up to 30s in the worst case, and 15s in the average case.
Cloud NAT 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, Identity and Access Management (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.
- On the Quotas page, select the quotas that you want to change.
- Click the Edit Quotas button at the top of the page.
- Fill out your name, email, and phone number, and then click Next.
- Fill in your quota request, and then 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 a 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 service level agreement (SLA) for the type of resource. For more information, review the relevant SLA for the resource.