Private network CLB is free of charge, while public network CLB is charged for instance fees and public network fees. If you purchase a CLB instance under a bill-by-IP account, two billing modes are supported: monthly subscription and pay-as-you-go.
Note:
Monthly subscription is currently in beta. This pricing document is for reference only, please see your bill for the actual price. If you wish to use this billing option, please contact sales.
Monthly subscription is prepaid. You need to pay for one or multiple months or even years in advance. This billing mode is applicable to long-term businesses with stable peak traffic. The public network fees of a monthly subscription CLB instance only supports bill-by-bandwidth, and the monthly bandwidth is cheaper than the hourly bandwidth. If you need to use CLB in the long run, we recommend purchasing the monthly subscription CLB instance.
You need to pay for the total purchased duration (in months) in advance.
The billable items include instance fees and public network fees.
Total fees = Instance fees + Public network fees = (Monthly instance fees * Purchased duration) + (Monthly bandwidth fees * Purchased duration)
Note:
- The network billing mode of a monthly subscription CLB instance only supports billing at a fixed bandwidth.
- You need to configure the bandwidth upper limit when purchasing a CLB instance with fixed bandwidth. This limit applies to both the outbound and inbound bandwidth. If exceeded, packets are lost by default and no fees will be incurred.
- Regardless of the actual bandwidth, the CLB instance is always billed by the configured bandwidth upper limit.
Region | Instance Fees (USD/Month) |
Bandwidth Fees (USD/Month) | |||||
---|---|---|---|---|---|---|---|
1 Mbps | 2 Mbps | 3 Mbps | 4 Mbps | 5 Mbps | 6 Mbps and above (`n` is the configured bandwidth upper limit) |
||
Guangzhou, Qingyuan, Shanghai, Nanjing, Beijing, Chengdu, Chongqing | 2.06 | 3.29 | 6.75 | 10.14 | 13.71 | 17.85 | 17.85 + 11.43 * (n-5) |
Hong Kong (China), Silicon Valley, Virginia, Toronto | 4.29 | 8.58 | 12.87 | 17.16 | 21.45 | 21.45 + 14.29 * (n - 5) | |
Singapore, Frankfurt, and Moscow | 3.29 | 6.58 | 9.87 | 13.16 | 16.45 | 16.45 + 11.43 * (n - 5) | |
Bangkok, Mumbai, Seoul, and Tokyo | 3.57 | 7.14 | 7.72 | 14.28 | 17.85 | 17.85 + 12 * (n - 5) |
Suppose you purchase a monthly subscription CLB instance in the Guangzhou region for 6 months and configure the bandwidth upper limit to 2 Mbps, which falls into the price tier of 6.75 USD/month:
Pay-as-you-go is an elastic billing mode, where you can create/terminate instances at any time and pay for what you use.
Instance fees and public network fees (dedicated bandwidth package):
If public network fees are billed by bandwidth package, the billing cycle will be monthly. For more information, please see Billing Overview.
The billable items include instance fees and public network fees.
The public network fees support both bill-by-traffic and bandwidth package.
The calculation formula of total public network fees varies by billing modes, as detailed below:
Billing Mode | Total Fees |
---|---|
Bill-by-traffic | Total fees = Instance fees (hourly instance fees * usage duration) + Public network fees (traffic fees per unit * total traffic) |
Bandwidth package | Total fees = Instance fees (hourly instance fees * usage duration) + Public network fees (bandwidth package fees) |
Region | Instance Fees (USD/Day) |
---|---|
Guangzhou, Qingyuan, Shanghai, Beijing, Chengdu and Chongqing | 0.07 |
Hong Kong (China), Seoul, Tokyo, Mumbai, and Bangkok | 0.22 |
Silicon Valley and Virginia | 0.12 |
Note:
- Fees for one billing cycle will be deducted in advance when you create a pay-as-you-go CLB instance. Make sure that your account balance is sufficient.
- You will be billed for hourly instance fees even when the CLB instance you purchased is in idle status (i.e., no access requests and no real server is bound).
Bill-by-traffic
This billing mode is based on the total volume (in GB) of data transferred over the public network and is applicable to scenarios where the business traffic fluctuates greatly. If your bandwidth utilization is below 10%, we recommend using bill-by-traffic.
Note:
- Currently, the outbound traffic is billable, i.e., traffic from CLB to the public network.
- To avoid fees incurred by sudden traffic surges, you can specify the bandwidth upper limit. If exceeded, packets are lost by default and no fees will be incurred.
Region | Public Network Fees (USD/GB) |
---|---|
Chinese mainland, Hong Kong (China), and Seoul | 0.12 |
Singapore | 0.081 |
Frankfurt, Toronto, and Silicon Valley | 0.077 |
Moscow and Tokyo | 0.13 |
Virginia | 0.075 |
Bangkok and Mumbai | 0.1 |
Bandwidth package
This billing mode bills multiple IPs in an aggregated manner and is applicable to large-scale businesses where public network instances have traffic peaks at different times.
For detailed pricing, please see Billing Overview.
Suppose you use a pay-as-you-go CLB instance whose public network billing mode is bill-by-traffic and the total traffic from CLB to the public network is 2 GB between 09:00:00, June 1, 2020 and 08:59:59, June 22, 2020 in the Guangzhou region, then:
Suppose you use a pay-as-you-go CLB instance whose public network billing mode is bandwidth package between 09:00:00, June 1, 2020 and 08:59:59, June 22, 2020 in the Guangzhou region, then:
Was this page helpful?