- 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
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 shared CLB instance will be increased to 50,000 concurrent connections, 5,000 new connections per second and 5,000 QPS
The performance is guaranteed for each CLB instance.
Note：
- Before the upgrade, shared CLB instances share resources of one cluster, which may affect the performance in case of resource contention.
- After the upgrade, the basic performance for every individual shared CLB instance is guaranteed. When the required performance exceeds the guaranteed value, resource contention may occur.
Price Adjustment
The price adjustment covers all CLB instances (former "Application Load Balancer instances") and Classic CLB instances.
- A private network CLB instance is priced as 0.686 USD per day (1.029 USD per day for some regions).
- A public network CLB instance is priced as 0.686 USD per day (1.029 USD per day for some regions).
See below for the new instance prices:
Prices provided in this notice take effect from 00:00:00, November 2, 2021 (UTC +8) until next price adjustment. This document describes only the price adjustments. For specific prices, see the pricing on purchase page or in your actual order.
| Billing Item | Billing Mode | Billing Cycle | Region | Price (Unit: USD/Day) |
|---|---|---|---|---|
| Instance fees | Pay-as-you-go | Day | Guangzhou, Shanghai, Nanjing, Beijing, Chengdu, Chongqing, Hong Kong (China), Singapore, Silicon Valley, Virginia, Toronto, Moscow, Jakarta | 0.686 |
| Bangkok, Mumbai, Seoul, Tokyo, Frankfurt | 1.029 |
NoteThe price adjustment may cause overdue payments, leading to account suspension and business interruption. Please delete unnecessary CLB instances based on your usage and monthly cost.
FAQs
How do I optimize my bill?
- Terminate idle CLB instances such as those without listeners or unbound to real servers.
- Each CLB can have up to 50 listeners. You can create multiple protocol ports for a single CLB instance. For more details, see Restrictions.
Yes
No
Was this page helpful?