Billing (Dedicated Load Balancers)

Billing Items

The following table describes the billing items of dedicated load balancers.

Table 2 describes the billing items.

• √ indicates that the billing item is involved. × indicates that the billing item is not involved.
• An LCU measures the dimensions on which a dedicated load balancer routes the traffic. The four dimensions measured are as follows:
  • New connections: the number of new connections that a dedicated load balancer establishes per second
  • Maximum concurrent connections: the maximum number of concurrent connections that a dedicated load balancer can handle
  • Queries per second: the number of Layer-7 HTTP or HTTPS requests that a dedicated load balancer routes to a backend server per second
  • Processed traffic: each GB of data transferred through a dedicated load balancer
• If you bind an EIP to a dedicated load balancer, you will also be charged for the EIP and the bandwidth used by the EIP.

  For details about EIP pricing, see Elastic IP Pricing Details.

Billing Mode

Dedicated load balancers provide Layer-4 packages and Layer-7 packages. You can select a Layer-4 package, a Layer-7 package, or both based on your requirements.

• The total bandwidth is the inbound or outbound bandwidth used for traffic to or from the backend servers.
• For details, see Table 2 and Table 3.

• Pay-per-use

  Formula: Total price = Load balancer price + LCU price

  • Load balancer price = Unit price ($0 USD/hour) x Usage duration
  • LCU price = Unit price ($0.00695 USD/hour) x LCUs in a single AZ x Number of AZs x Usage duration

  The following table lists of the number of LCUs and their prices in different specifications in the pay-per-use mode.

  Table 3 Dedicated load balancer for network load balancing (TCP/UDP)

  Type	LCUs in an AZ	Load Balancer Unit Price (Hourly)	LCU Unit Price (Hourly)	Load Balancer Price (Hourly)	LCU Price (Unit Price x Number of AZs)
  Small I	10	0	0.00695	0	0.0695
  Small II	20	0	0.00695	0	0.139
  Medium I	40	0	0.00695	0	0.278
  Medium II	80	0	0.00695	0	0.556
  Large I	200	0	0.00695	0	1.39
  Large II	400	0	0.00695	0	2.78

  Table 4 Dedicated load balancers for application load balancing (HTTP/HTTPS)

  Type	LCUs in an AZ	Load Balancer Unit Price (Hourly)	LCU Unit Price (Hourly)	Load Balancer Price (Hourly)	LCU Price (Unit Price x Number of AZs)
  Small I	10	0	0.00695	0	0.0695
  Small II	20	0	0.00695	0	0.139
  Medium I	40	0	0.00695	0	0.278
  Medium II	100	0	0.00695	0	0.695
  Large I	200	0	0.00695	0	1.39
  Large II	400	0	0.00695	0	2.78

  

  • 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 = Number of LCUs in the selected specification x Number of the selected AZs.
  • You need to select at least an AZ when you create a dedicated load balancer. For more information about AZs, see Region and AZ.

  Example:

  If you select small I for network load balancing and small II for application load balancing and deploy the load balancer in two AZs, the total price for using the load balancer for 3 hours is calculated as follows:

  Load balancer price + LCU price = $0/hour x 3 hours + ($0.0695/hour + $0.139/hour) x 2 AZs x 3 hours = $1.251

Changing the Billing Configuration

Ticket Management

• Load balancers support only pay-per-use billing. The billing mode cannot be changed.
• Submit a service ticket.

  New specifications take effect immediately upon change. You are then charged based on the new specifications.

Renewal

You can renew your resources on the Renewals page after logging in to the management console. For details, see Renewal Management.

Expiration and Overdue Payment

If your account is in arrears, you can view the arrears details in the Billing Center. To prevent your load balancers from being stopped or released, top up your account in a timely manner. For details, see Repaying Outstanding Amount.

If you do not renew your load balancers in time, your account will be frozen and your load balancers will be kept in retention.

During this period, the load balancers cannot be used. For details, see What Functions Will Become Unavailable If a Load Balancer Is Frozen?

If you still do not complete the renewal or payment after the retention period ends, your data stored in cloud services will be deleted and the resources will be released.