This document lists the quotas and system limits that apply to Cloud Load Balancing.
- Quotas have default values, but you can typically request adjustments.
- System limits are fixed values that can't be changed.
To change a quota, see Request additional quota.
Google Cloud uses quotas to help ensure fairness and reduce spikes in resource use and availability. A quota restricts how much of a Google Cloud resource your Google Cloud project can use. Quotas apply to a range of resource types, including hardware, software, and network components. For example, quotas can restrict the number of API calls to a service, the number of load balancers used concurrently by your project, or the number of projects that you can create. Quotas protect the community of Google Cloud users by preventing the overloading of services. Quotas also help you to manage your own Google Cloud resources.
The Cloud Quotas system does the following:
- Monitors your consumption of Google Cloud products and services
- Restricts your consumption of those resources
- Provides a way to request changes to the quota value and automate quota adjustments
In most cases, when you attempt to consume more of a resource than its quota allows, the system blocks access to the resource, and the task that you're trying to perform fails.
Quotas generally apply at the Google Cloud project level. Your use of a resource in one project doesn't affect your available quota in another project. Within a Google Cloud project, quotas are shared across all applications and IP addresses.
For more information, see the Cloud Quotas overview.
There are also system limits on Cloud Load Balancing resources. System limits can't be changed.
Backends
| Item | Quotas and limits | Notes |
|---|---|---|
| Instance groups | Quota | Quotas are per-project and per-region. When making a quota increase request, select the region that contains the instance group. Zonal instance groups charge the region containing the instance group's zone. |
| Zonal and regional NEGs per project | Quota | Quotas are per-project and per-region, covering all types of NEGs except for global internet NEGs, Private Service Connect NEGs, and serverless NEGs. When making a quota increase request, select the region that contains the NEG. Zonal NEGs charge the region containing the NEG's zone. |
| Global NEGs per project | Quota | This quota is global, per-project, and covers global internet NEGs, Private Service Connect NEGs, and serverless NEGs. |
Maximum number of instance group backends, GCE_VM_IP_PORT
NEG backends, GCE_VM_IP NEG backends, or regional internet NEG
backends per backend service |
50 |
This limit is not configurable. Support for zonal and internet NEG backends varies by load balancing product. If you have configured failover
for backend service-based
regional external passthrough Network Load Balancers or if you have configured failover for
internal passthrough Network Load Balancers, you can configure up to 50 primary and 50 backup
instance groups or Internal passthrough Network Load Balancers also have a limit on the number of individual virtual machine (VM) instances or endpoints to which a backend service can distribute packets. For more information, see backend services. |
Maximum number of instance group backends or GCE_VM_IP NEG
backends per backend service of a global external passthrough Network Load Balancer |
25 | This limit is not configurable. |
Endpoints per NEG
| Item | Quotas and limits | Notes |
|---|---|---|
Endpoints per GCE_VM_IP_PORT zonal NEG |
10,000 | This limit cannot be increased. |
Endpoints per GCE_VM_IP zonal NEG |
10,000 | This limit cannot be increased. |
Endpoints per hybrid connectivity NEG (NON_GCP_PRIVATE_IP_PORT) |
10,000 | This limit cannot be increased. |
| Endpoints per global internet NEG | 1 | This limit cannot be increased. |
| Endpoints per regional internet NEG | 256 | This limit cannot be increased. |
| Endpoints per serverless NEG | 1 | This limit cannot be increased. |
| Endpoints per Private Service Connect NEG | 1 | This limit cannot be increased. |
| Endpoints per port mapping NEG | 1,000 | This limit cannot be increased. |
VMs per instance group
The number of backend VMs that can be serviced by a single load balancer might be less than the number of VMs that an instance group can support. The maximum number of load-balanced VMs per instance group depends on the number of ports specified in each named port that the instance group exports.
By default, the upper limit of load-balanced VMs per instance group cannot exceed 2,000 for regional managed instance groups (MIGs), and cannot exceed 1,000 for zonal MIGs. In zonal unmanaged instance groups, the maximum number of VMs per group is 2,000. If you need more than 2,000 VMs, you can increase the size limit of your managed instance group or contact support.
| Item | Quotas and limits | Notes |
|---|---|---|
| Maximum number of VMs per regional managed instance group connected to a pass-through load balancer's backend service | 2,000 | Internal passthrough Network Load Balancers also have a limit on the number of individual VM instances or endpoints to which a backend service can distribute packets. For details, see backend services. |
| Maximum number of VMs per zonal managed instance group or per zonal unmanaged instance group connected to a pass-through load balancer's backend service | Maximum for zonal managed instance groups: 1,000 Maximum for zonal unmanaged instance groups: 2,000 |
Internal passthrough Network Load Balancers also have a limit on the number of individual VM instances or endpoints to which a backend service can distribute packets. For details, see backend services. |
| Maximum number of VMs per regional managed instance group connected to a proxy load balancer's backend service | Depends on the number of ports specified in the named port for the
instance group. It is the smaller of these two: A: 2,000 B: 10,000 / (number of ports in the named port that contains the most port numbers)* |
Contact support if you need to increase this limit. |
| Maximum number of VMs per zonal managed instance group connected to a proxy load balancer's backend service | Depends on the number of ports specified in the named port for the
instance group. It is the smaller of these two: A: 1,000 B: 10,000 / (number of ports in the named port that contains the most port numbers)* |
Contact support if you need to increase this limit. |
| Maximum number of VMs per zonal unmanaged instance group connected to a proxy load balancer's backend service | Depends on the number of ports specified in the named port for the
instance group. It is the smaller of these two: A: 2,000 B: 10,000 / (number of ports in the named port that contains the most port numbers)* |
Contact support if you need to increase this limit. |
* To calculate the maximum number of load-balanced VMs in an instance group backend:
Determine maximum number of ports per named port.
For example, if an instance group has the following named ports:
http:80,api-gateway:8080, andapi-gateway:8090, then there is one port number for thehttpname and two port numbers for theapi-gatewayname. Therefore, in this example the maximum number of ports per named port is two.Divide 10,000 by the maximum number of ports per named port and discard the remainder. For example,
10,000 / 2 = 5,000.Compare the number calculated in the previous step with the upper limit of load-balanced VMs per instance group: 2,000 for regional groups, 1,000 for zonal groups.
If the number calculated in the previous step is less than or equal to the upper limit, then the maximum number of load-balanced VMs per instance group is the number you calculated in the previous step. Otherwise, the maximum number of load-balanced VMs per instance group is the upper limit (2,000 for regional groups or 1,000 for zonal groups).
Target pools
| Item | Quotas and limits | Notes |
|---|---|---|
| Target pools | Quota | This quota is per project. |
Backend buckets
These quotas apply to Application Load Balancers.
| Item | Quotas and limits | Notes |
|---|---|---|
| Backend buckets | Quota | This quota is per project. |
| Global internal managed backend buckets | Quota | This is a per-project quota. Quota name: Available metrics:
|
| Regional external managed backend buckets | Quota | This is a per-project quota. Quota name: Available metrics:
|
| Regional internal managed backend buckets | Quota | This is a per-project quota. Quota name: Available metrics:
|
Backend services
To monitor backend service quotas using Cloud Monitoring, set up monitoring
for the serviceruntime.googleapis.com/quota/allocation/usage metric on the
Consumer Quota resource type. Set additional label filters (service,
quota_metric) to get to the quota type. For information about how to monitor
quota usage metrics, see
Chart and monitor quota metrics.
| Item | Quotas and limits | Notes |
|---|---|---|
| Application Load Balancers and Proxy Network Load Balancers | ||
| Classic Application Load Balancer and Classic proxy Network Load Balancer backend services | Quota | This is a per-project quota defining the maximum number of backend services for classic Application Load Balancers and classic proxy Network Load Balancers. Quota name: Available metrics:
|
| Global external Application Load Balancer and Global external proxy Network Load Balancer backend services | Quota | This is a per-project quota defining the maximum number of backend services for global external Application Load Balancers and global external proxy Network Load Balancers. Quota name: Available metrics:
|
Regional external Application Load Balancer and Regional external proxy Network Load Balancer backend services |
Quota | This is a per-region and per-project quota defining the maximum number of backend services for regional external Application Load Balancers and global external proxy Network Load Balancers. Quota name: Available metrics:
|
| Cross-region internal Application Load Balancer and Cross-region internal proxy Network Load Balancer backend services | Quota | This is a per-region and per-project quota defining the maximum number of backend services for cross-region internal Application Load Balancers and cross-region internal proxy Network Load Balancers. Quota name:
Available metrics:
|
| Regional internal Application Load Balancer and Regional internal proxy Network Load Balancer backend services | Quota | This is a per-region and per-project quota defining the maximum number of backend services for regional internal Application Load Balancers and regional internal proxy Network Load Balancers. Quota name: Available metrics:
|
| Number of backend services per Application Load Balancer | Varies based on the URL map configuration | For more details, see URL maps. |