- 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 describes the use limits of CLB.
General Restrictions
The use of Tencent Cloud CLB has certain restrictions, and different types of CLB instances have their own use limits. For more information on CLB instance types, see Instance Types.
| Instance Type | Resource | Default Restriction |
|---|---|---|
| General restrictions for all instances | Number of public network CLB instances that can be created in a single region |
|
| Number of private network instances that can be created under one account in a single region | 100 | |
| Number of listeners that can be added to an instance | 50 | |
| Ports that can be selected by a listener in an instance | An integer between 1 and 65535 | |
| CLB (formerly "application CLB") |
Number of domain name and URL forwarding rules that can be configured for an HTTP/HTTPS listener in a CLB instance | 50 |
| Number of servers that can be bound to a forwarding rule in a CLB instance | 100 | |
| Number of backend ports that can correspond to a frontend port of a CLB instance | Multiple ports | |
| Classic CLB | Number of servers that can be bound to a listener in a classic CLB instance | 100 |
| Number of backend ports that can correspond to a frontend port of a classic CLB instance | 1 port |
A CLB instance will not unbind itself from the CVM instance. After a CVM instance becomes isolated (pay-as-you-go CVM instance has been in arrears for more than 2 hours), it will not unbind itself from the CLB instance either.
Peak Bandwidth
The meaning of peak bandwidth varies by network billing modes as detailed below:
| Billing Mode | Difference | Description |
|---|---|---|
| Billed by fixed bandwidth (including hourly bandwidth subscription and monthly bandwidth) |
This peak bandwidth is the committed bandwidth, and is guaranteed in case of bandwidth competition. | The sum of peak bandwidth of all the running instances that are billed at a fixed bandwidth (including hourly-subscribed bandwidth and monthly-subscribed bandwidth) cannot exceed 50 Gbps in one region. If you require a higher bandwidth, contact your sales rep. |
| Bill-by-traffic | The peak bandwidth is only regarded as the maximum peak bandwidth, and not as the committed bandwidth. When bandwidth resources are contested, the peak bandwidth may be limited. | The sum of peak bandwidth of all the running bill-by-traffic instances cannot exceed 5 Gbps in one region. If your application requires a guaranteed or higher bandwidth, choose bill-by-bandwidth. |
| Bandwidth packages | The sum of peak bandwidth of all the running instances that are billed by shared bandwidth package cannot exceed 50 Gbps in one region. If you require a higher bandwidth, contact your sales rep. |
Yes
No
Was this page helpful?