Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Application Load Balancer
  • Getting started
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • L7 load balancer logs
  • Release notes

In this article:

  • What goes into the cost of using Application Load Balancer
  • Cost calculation example
  • Prices for the Russia region

Yandex Application Load Balancer pricing policy

Written by
Yandex Cloud
Updated at December 2, 2025
  • What goes into the cost of using Application Load Balancer
    • Cost calculation example
  • Prices for the Russia region

To estimate your service costs, see the pricing in this section.

The prices for service products are also available in the price list.

Note

Currency of Service rates (prices) depends on the company you made a contract with:

  • Prices in US dollars are applicable to customers of Iron Hive doo Beograd (Serbia) or Direct Cursus Technology L.L.C. (Dubai).
  • Prices in Russian roubles are applicable to customers of Yandex.Cloud LLC.

All prices below do not include VAT.

What goes into the cost of using Application Load BalancerWhat goes into the cost of using Application Load Balancer

When using the Application Load Balancer service, you pay for the actual use of computing resources of every active load balancer.

The amount of used resources is determined by the number of resource units, i.e., internal VMs provisioned for the load balancer in each availability zone.

One resource unit supports these peak performance thresholds:

  • 1000 requests per second (RPS).
  • 4000 concurrently active connections.
  • 300 new connections per second.
  • 22 MB (176 Mbit) of traffic per second (covers both incoming and outgoing traffic).

The system automatically scales the resource unit group based on the load balancer node’s external workload. The system calculates the group size to ensure resource unit utilization remains below specified thresholds.

You can limit the number of load balancer resource units in its autoscaling settings. By default, each availability zone requires at least two units, while the total number of units across all zones is unlimited. You cannot set a limit lower than two resource units per zone.

The load balancer usage is billed hourly. You are charged for the maximum number of resource units that were running for an hour. When creating an L7 load balancer, you can see its cost calculation in the management console on the right.

Cost calculation exampleCost calculation example

A load balancer operates within a single availability zone. We use the default auto-scaling settings with the minimum of two resource units per zone and no limit on the maximum total number of units.

The load balancer has been running for an hour. The inbound traffic reached these peak values at various timestamps:

  • 6,000 RPS.
  • 29,000 concurrently active connections.
  • 750 new connections per second.
  • 20 MB of traffic per second.

This workload requires eight resource units to process:

  • 6,000 / 1,000 = 6 resource units per 6,000 RPS.
  • 29,000 / 4,000 = 7.25 ≈ 8 resource units per 30,000 active connections.
  • 750 / 300 = 2.5 ≈ 3 resource units per 750 new connections.
  • 20 / 22 = 0.9090... ≈ 1 resource unit per 20 MB/sec of traffic.

Calculating cost per hour:

8 × $0.019980 = $0.159840

Total: $0.159840, cost of using a load balancer per hour.

Where:

  • 8: Number of resource units.
  • $0.019980: Price per resource unit.

30-day cost estimate for this hourly workload:

$0.159840 × 720 = $115.084800

Total: $115.084800, cost of using a load balancer per month.

Where:

  • $0.159840: Cost of using a load balancer per hour.
  • 720: Number of hours per month.

Prices for the Russia regionPrices for the Russia region

Note

Yandex Cloud resources are priced differently in different regions. For more information about the available regions, see Regions.

Your payment currency is determined by your contracting legal entity. For more information on creating an account, see Registering an account in Yandex Cloud.

Number Price per hour, without VAT
One resource unit $0.019980

Was the article helpful?

Previous
Access management
Next
Overview
© 2025 Direct Cursus Technology L.L.C.