- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- CLB Instance
- CLB Listener
- CLB Listener Overview
- Configuring TCP Listener
- Configuring UDP Listener
- Configuring TCP SSL Listener
- Configuring QUIC Listener
- Configuring HTTP Listener
- Configuring HTTPS Listener
- Load Balancing Methods
- Session Persistence
- Layer-7 Redirection Configuration
- Layer-7 Custom Configuration
- Layer-7 Domain Name Forwarding and URL Rules
- Using QUIC Protocol on CLB
- SNI Support for Binding Multiple Certificates to a CLB Instance
- Real Server
- Health Check
- Certificate Management
- Monitoring and Alarm
- Log Management
- Cloud Access Management
- Classic CLB
- Best Practices
- Enabling Gzip Configuration & Testing
- HTTPS Forwarding Configurations
- Obtaining Real Client IPs
- Notes on SNAT and Non-SNAT Types for Private Network CLB
- Implementing HA Across Multiple AZs
- Load Balancing Algorithm Selection and Weight Configuration Examples
- Configuring WAF protection for CLB listening domain names
- Troubleshooting
- OPS Guidelines
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- Listener APIs
- Real Server APIs
- Target Group APIs
- Redirection APIs
- Other APIs
- Cloud Load Balancer APIs
- Classic CLB APIs
- Data Types
- Error Codes
- CLB API 2017
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- CLB Instance
- CLB Listener
- CLB Listener Overview
- Configuring TCP Listener
- Configuring UDP Listener
- Configuring TCP SSL Listener
- Configuring QUIC Listener
- Configuring HTTP Listener
- Configuring HTTPS Listener
- Load Balancing Methods
- Session Persistence
- Layer-7 Redirection Configuration
- Layer-7 Custom Configuration
- Layer-7 Domain Name Forwarding and URL Rules
- Using QUIC Protocol on CLB
- SNI Support for Binding Multiple Certificates to a CLB Instance
- Real Server
- Health Check
- Certificate Management
- Monitoring and Alarm
- Log Management
- Cloud Access Management
- Classic CLB
- Best Practices
- Enabling Gzip Configuration & Testing
- HTTPS Forwarding Configurations
- Obtaining Real Client IPs
- Notes on SNAT and Non-SNAT Types for Private Network CLB
- Implementing HA Across Multiple AZs
- Load Balancing Algorithm Selection and Weight Configuration Examples
- Configuring WAF protection for CLB listening domain names
- Troubleshooting
- OPS Guidelines
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- Listener APIs
- Real Server APIs
- Target Group APIs
- Redirection APIs
- Other APIs
- Cloud Load Balancer APIs
- Classic CLB APIs
- Data Types
- Error Codes
- CLB API 2017
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
This document explains the billing of bill-by-IP accounts and provides related billing examples.
Billable Items
For bill-by-IP accounts, the CLB cost involves the following four parts: instance fee, public network fee, cross-region binding fee and LCU fee.
Note：
- Only LCU-supported CLB instances incur LCU usage fees. LCU-supported CLB instances are only available to beta users now. To use it, please submit an application.
- Shared CLB instances are free of LCU charges.
| Account Type | Network Type | Instance Type | Instance Fee | Public Network Fee | Cross-region Binding Fee | LCU Fee |
|---|---|---|---|---|---|---|
| Bill-by-IP | Public network | Shared | ✓ | ✓ | ✓ | - |
| LCU-supported | ✓ | |||||
| Private network | Shared | ✓ | - | - | - | |
| LCU-supported | ✓ |
- Private network CLB is free of public network fee but generates instance fee. For more details, see CLB Instance Upgrade and Price Adjustment.
- Public network CLB generates instance fee and public network fee.
- If cross-region binding 2.0 is configured and enabled for public network CLB instances, the cross-region binding fee is included in the CNN bill.
Note：Tencent Cloud plans to upgrade the architecture of all CLB instances staring from 00:00:00, November 2, 2021 (UTC +8). After the upgrade, the guaranteed performance of each individual CLB instance will be increased to 50,000 concurrent connections, 5,000 new connections per second and 5,000 QPS. The new unit price for CLB instances (both private and public network) is 0.686 USD/day for most regions, and 1.029 USD/day for the rest regions. See CLB Instance Upgrade and Price Adjustment for more details.
Pay-As-You-Go
The CLB cost is calculated on the actual amount of usage.
Pricing
CLB cost = Instance fee + Public network fee + LCU fee
Instance fee
The instance fee is billed by hour and settled once every hour. Each partial hour is billed as a full hour.
| Region | Instance Fee (Unit: USD/Day) |
|---|---|
| Guangzhou, Shanghai, Nanjing, Beijing, Chengdu, Chongqing, Hong Kong (China), Singapore, Jakarta, Silicon Valley, Virginia, Toronto, Moscow | 0.686 |
| Bangkok, Mumbai, Seoul, Tokyo, Frankfurt, Sao Paulo | 1.029 |
Note：
- Fee for one settlement cycle will be deducted in advance when you create a pay-as-you-go CLB instance. Make sure that your account balance is sufficient.
- The CLB instance will incur hourly instance fees even when it is idle (i.e., there is no access requests and no real server is bound).
Public network fee
Bill by traffic
展开&收起This billing mode is based on the total volume of data (in GB) transferred over the public network and settled once every hour, which 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 unexpected costs due to traffic surges, you can set a bandwidth cap. Any traffic over the cap is dropped and does not incur charges.
- The traffic units are 1024-based. For example, 1 TB = 1,024 GB, and 1 GB = 1,024 MB.
| Region | Public Network Fee (Unit: USD/GB) |
|---|---|
| Chinese mainland, Seoul, Hong Kong (China), Jakarta | 0.12 |
| Singapore | 0.081 |
| Frankfurt, Toronto, Silicon Valley | 0.077 |
| Moscow, Tokyo | 0.13 |
| Virginia | 0.075 |
| Bangkok, Mumbai | 0.1 |
| São Paulo | 0.15 |
Bill by BWP
展开&收起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 more details about the pricing, see BGP Bandwidth Package.
LCU fee
For more details on how LCU is billed in the pay-as-you-go modal, see LCU Billing.
Billing samples
Shared
展开&收起Sample 1 (public network is billed by traffic)
Suppose you use a pay-as-you-go CLB instance with bill-by-traffic public network and the total traffic from CLB to the public network is 2 GB between June 1st 10:00:00 and June 2nd 09:59:59 in Guangzhou.
- Total instance fee = Unit price × Usage duration, that is 0.686 USD/day × 1 day = 0.686 USD.
- Total public network fee = Unit price × Total traffic, that is 0.12 USD/GB × 2 GB = 0.24 USD.
Total fee = Instance fee + Public network fee, that is 0.686 USD + 0.24 USD = 0.926 USD.
Sample 2 (public network is billed by bandwidth package)
Suppose you use a pay-as-you-go CLB instance with bill-by-BWP public network between June 1st 10:00:00 and June 2nd 09:59:59 in Guangzhou.
- Total instance fee = Unit price × Usage duration, that is 0.686 USD/day × 1 day = 0.686 USD.
- Total public network fee for this period cannot be settled because BWP fees are settled monthly.
Total fee = Instance fee, that is 0.686 USD.
LCU-supported
展开&收起Sample 1 (public network is billed by traffic)
Suppose you use a pay-as-you-go CLB instance with bill-by-traffic public network, the total traffic from CLB to the public network is 2 GB between June 1st 10:00:00 and June 2nd 09:59:59 in Guangzhou and the average LCUs used per hour is 2 LCUs.
- Total instance fee = Unit price × Usage duration, that is 0.686 USD/day × 1 day = 0.686 USD.
- Total public network fee = Unit price × Total traffic, that is 0.12 USD/GB × 2 GB = 0.24 USD.
- Total LCU fee = 2 LCUs × 0.0072 USD/LCU/hour × 24 hour = 0.3456 USD.
Total fee = Instance fee (0.686 USD) + Public network fee (0.24 USD) + LCU fee (0.3456 USD) = 1.2716 USD.
Sample 2 (public network is billed by bandwidth package)
Suppose you use a pay-as-you-go CLB instance with bill-by-BWP public network between June 1st 10:00:00 and June 2nd 09:59:59 in Guangzhou and the average LCUs used per hour is 2 LCUs.
- Total instance fee = Unit price × Usage duration = 0.686 USD/day × 1 day = 0.686 USD.
- Total public network fee for this period cannot be settled because BWP fees are settled monthly.
- Total LCU fee = 2 LCUs × 0.0072 USD/LCU/hour × 24 hour = 0.3456 USD.
Total fee = Instance fee (0.686 USD) + LCU fee (0.0144 USD) = 1.0316 USD.
Yes
No
Was this page helpful?