Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Network Load Balancer
  • Getting started
    • Overview
    • Network load balancer types
    • Traffic listener
    • Target groups and resources
    • Health checks
    • Implementation specifics
    • Use cases
    • Recommendations for use
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ
  1. Concepts
  2. Quotas and limits

Quotas and limits in Network Load Balancer

Written by
Yandex Cloud
Updated at May 5, 2025

Yandex Network Load Balancer has the following limits:

  • Quotas are organizational constraints that our support team can change upon request.
  • Limits are technical constraints of the Yandex Cloud architecture. You cannot change the limits.

If you need more resources, you can increase your quotas in one of the following ways:

  • Make a request to increase your quotas.
  • Contact support, detailing which quotas you want increased and by how much.

To have your request processed, you must have the quota-manager.requestOperator role or higher, e.g.,editor or admin.

You can manage quotas using Cloud Quota Manager.

QuotasQuotas

Type of limitation Value
Number of load balancers per cloud 2
Number of target groups per cloud 100

LimitsLimits

Type of limitation Value
Number of targets per target group 254
Number of ports per listener 10
Number of health checks per attached target group 1
Health check protocol TCP, HTTP

Other restrictionsOther restrictions

A single target group can only contain targets from a single cloud network.

Within a single availability zone, a target group can only include targets on the same subnet.

If you add a target to the internal load balancer's target group, it will not be directly accessible on the target port.

You can create a load balancer without a listener.

Health check traffic comes from the 198.18.235.0/24 and 198.18.248.0/24 ranges.

When adding targets for a load balancer, keep in mind the limit on the maximum number of concurrent TCP/UDP connections per VM.

Was the article helpful?

Previous
Recommendations for use
Next
Access management
© 2025 Direct Cursus Technology L.L.C.