Billing Items (Dedicated Load Balancers)

Billing

You will be charged for how many LCUs you use and how long a load balancer is retained in your account, as described in Table 1.

For details about the prices of billing items, see the pricing details on the creation page on the console.

Table 1 Billing items

Billing Item	Description	Billing Mode	Formula
LCU	You are charged based on the number of LCUs used by a load balancer per hour. An LCU measures the dimensions on which a dedicated load balancer routes the traffic. See LCU prices in LCU Pricing.	Pay-per-use	Unit price x Number of LCUs x Required duration
Load Balancer	You are charged for how long a dedicated load balancer is retained in your account. If the load balancer is retained in your account for less than 1 hour, you will be charged for the actual duration, accurate to seconds.	Pay-per-use	Unit price x Required duration

The billing items of dedicated load balancers vary by specification type. For details, see Table 2.

Table 2 Varied billing items by billing mode

Billing Mode	Specifications	LCU	Load Balancer
Pay-per-use	Elastic	Y	Y
	Fixed	Y	x

Note

• Y indicates that the billing item is involved. x indicates that the billing item is not involved.

• If you bind an EIP to a load balancer, you will also be charged for the EIP and the bandwidth used by the EIP.

LCU Pricing

An LCU measures the dimensions on which a dedicated load balancer routes the traffic. See LCU price in Table 3.

The unit price of LCU varies depending on the billing mode and specifications. See the actual price of LCU on the console. LCU price = Unit price x Number of LCUs x Required duration.

Table 3 LCU pricing

Billing Mode	Specifications	Application Scenario	Description
Pay-per-use	Elastic	For fluctuating traffic	You are charged for how many LCUs you use.
	Fixed	For stable traffic	You are charged for the LCUs based on each fixed specification you select.

Note

• If you deploy a dedicated load balancer in multiple AZs, its performance will multiply as the number of AZs increases.

• Note the following when calculating the number of LCUs:

  • LCU quantity refers to the number of LCUs corresponding to a specification in a single AZ.

  • If you select multiple AZs for a load balancer, the number of LCUs is calculated as follows: Number of LCUs = LCUs of the selected specification x Number of the selected AZs.

LCU Billing for Elastic Specifications

An LCU has four dimensions: new connections, maximum concurrent connections, processed bytes, and rule evaluations.

You can calculate the number of LCUs by taking the maximum LCUs consumed across the four dimensions.

Note

The number of LCUs is rounded up to the nearest integer.

Table 4 LCU dimensions

Dimension	Description
New connections	Number of new connections per second.
Maximum concurrent connections	The maximum number of concurrent connections that a load balancer can handle per minute.
Processed bytes	The number of bytes processed by a load balancer in GB.
Rule evaluations (application load balancing)	The product of the number of rules processed by a load balancer and the number of queries per second (QPS). The first 10 processed rules are free. When there are more than 10 processed rules, the number of rule evaluations is calculated as follows: Rule evaluations = QPS x (Number of processed rules - 10). When there are 10 or less processed rules, the number of rule evaluations is equal to the QPS.

Table 5 lists the LCU performance supported by different protocols.

Table 5 LCU performance supported by different protocols

Protocol	New Connections per Second	Maximum Concurrent Connections per Minute	Processed Bytes	Rule Evaluations per Second
TCP	800	100,000	1 GB	N/A
UDP	400	50,000	1 GB	N/A
HTTP/HTTPS	25	3,000	1 GB	1,000

Load Balancer Pricing

You are charged for how long each load balancer is retained in your account. If the load balancer is used for less than 1 hour, you will be charged for the actual duration, accurate to seconds. The billing cycle is from the time when the dedicated load balancer is created to the time when it is deleted.

Only load balancers with elastic specifications in pay-per-use billing mode are charged.

last updated: 2025-02-21 14:17 UTC - commit: 5a77f21602a52bbd1e49e761ea9989d98b140b8f