tencent cloud

Cloud Load Balancer

Release Notes and Announcements
CLB Release Notes
Product Announcements
Product Introduction
Overview
Strengths
Use Cases
Principles
Product Comparison
Use Limits
Service Regions and Service Providers
Purchase Guide
Billing Overview
Billing
CLB Resource Package
Purchase Methods
Payment Overdue
Product Attribute Selection
Getting Started
Getting Started with Domain Name-Based CLB
Getting Started with CLB
Getting Started with IPv6 CLB
Deploying Nginx on CentOS
Deploying Java Web on CentOS
Operation Guide
CLB Instance
CLB Listener
Real Server
Health Check
Certificate Management
Log Management
Monitoring and Alarm
Cloud Access Management
Classic CLB
Practical Tutorial
Deploy certificate to CLB (mutual authentication)
Enabling Gzip Compression & Testing
HTTPS Forwarding Configurations
Obtaining Real Client IPs
Best Practices for Configuring Load Balancing Monitoring Alerts
Implementing HA Across Multiple AZs
Load Balancing Algorithm Selection and Weight Configuration Examples
Configuring WAF protection for CLB listening domain names
Configure IAP to authenticate web access to the CLB domain and path
Configure IAP to authenticate programmatic access to CLB's domain and path
Ops Guide
Solution to Excessive Clients in TIME_WAIT Status
Load Balancer HTTPS Service Performance Test
Stress Testing FAQ
CLB Certificate Operation Permissions
Troubleshooting
UDP Health Check Exception
API Documentation
History
Introduction
API Category
Instance APIs
Listener APIs
Backend Service APIs
Target Group APIs
Redirection APIs
Other APIs
Classic CLB APIs
Load Balancing APIs
Making API Requests
Data Types
Error Codes
CLB API 2017
FAQs
Billing
CLB Configuration
Troubleshooting Health Check Issues
HTTPS
WS/WSS Protocol Support
HTTP/2 Protocol Support
Default Domain Name Blocking Prompt
Service Level Agreement
Contact Us
Glossary

Use Limits

PDF
Focus Mode
Font Size
Last updated: 2025-05-16 09:55:46
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
100 general IP-based instances
3 static IP-based instances under one individual account or 15 under one organizational account.
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:
Note:
All network billing modes:
When the outbound bandwidth purchased by the user is less than or equal to 10 Mbps, Tencent Cloud allocates 10 Mbps of public network inbound bandwidth.
When the outbound bandwidth purchased by the user is greater than 10 Mbps, Tencent Cloud allocates public network inbound bandwidth equal to the purchased outbound bandwidth.
Billing Mode
Difference
Description
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.


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback