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
DocumentationCloud Load BalancerPurchase GuideBillingInstance Pricing

Instance Pricing

PDF
Focus Mode
Font Size
Last updated: 2025-11-27 16:14:33
An CLB instance incurs the instance fee even when it is idle (i.e., there are no access requests and no real server is bound).

Pay-as-You-Go

Billing cycle

The instance fee is calculated and billed on a daily basis.
Billing starts when the CLB instance is created successfully and ends when the termination task is initiated.
The minimum billable period is one hour.
Note:
When you create a pay-as-you-go CLB instance, an hour of instance fee (1/24 of the daily unit price) is deducted from your account balance. Make sure that your account balance is sufficient.

Pricing

Region
Instance fee (USD/hour)
Seoul, Mumbai, Virginia
0.0214
Tokyo
0.0231
Singapore, Jakarta, Silicon Valley
0.0239
Frankfurt, Hong Kong (China), Riyadh
0.0257
Guangzhou, Shanghai, Nanjing, Beijing, Chengdu, Chongqing
0.0286
São Paulo
0.0323
Bangkok, Shanghai ADC
0.0429

See also


Previous Topic: Billing OverviewNext Topic: Network Pricing

Help and Support

Was this page helpful?

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

Feedback