tencent cloud

TDSQL-C for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
Beginner's Guide
Product Introduction
Overview
Strengths
Use Cases
Architecture
Product Specifications
Instance Types
Product Feature List
Database Versions
Regions and AZs
Common Concepts
Use Limits
Suggestions on Usage Specifications
Kernel Features
Kernel Overview
Kernel Version Release Notes
Optimized Kernel Version
Functionality Features
Performance Features
Security Features
Stability Feature
Analysis Engine Features
Inspection and Repair of Kernel Issues
Purchase Guide
Billing Overview
Product Pricing
Creating Cluster
Specification Adjustment Description
Renewal
Payment Overdue
Refund
Change from Pay-as-You-Go to Yearly/Monthly Subscription
Change from Pay-as-You-Go to Serverless Billing
Value-Added Services Billing Overview
Viewing Billing Statements
Getting Started
Database Audit
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Logs
Log Shipping
Post-Event Alarm Configuration
Modifying Audit Rule
Modifying Audit Service
Disabling Audit Service
Audit Rule Template
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
Serverless Service
Serverless Introduction
Creating and Managing a Serverless Cluster
Elastic Scaling Management Tool
Serverless Resource Pack
Multi-AZ Deployment
Configuration Change
FAQs
Serverless Cost Estimator
Operation Guide
Operation Overview
Switching Cluster Page View in Console
Database Connection
Instance Management
Configuration Adjustment
Instance Mode Management
Cluster Management
Scaling Instance
Database Proxy
Account Management
Database Management
Database Management Tool
Parameter Configuration
Multi-AZ Deployment
GD
Backup and Restoration
Operation Log
Data Migration
Parallel Query
Columnar Storage Index (CSI)
Analysis Engine
Database Security and Encryption
Monitoring and Alarms
Basic SQL Operations
Connecting to TDSQL-C for MySQL Through SCF
Tag
Practical Tutorial
Classified Protection Practice for Database Audit of TDSQL-C for MySQL
Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
Usage Instructions for TDSQL-C MySQL
New Version of Console
Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
Strengths of Database Proxy
Selecting Billing Mode for Storage Space
Creating Remote Disaster Recovery by DTS
Creating VPC for Cluster
Data Rollback
Solution to High CPU Utilization
How to Authorize Sub-Users to View Monitoring Data
White Paper
Security White Paper
Performance White Paper
Troubleshooting
Connection Issues
Performance Issues
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Multi-Availability Zone APIs
Other APIs
Audit APIs
Database Proxy APIs
Backup and Recovery APIs
Parameter Management APIs
Billing APIs
serverless APIs
Resource Package APIs
Account APIs
Performance Analysis APIs
Data Types
Error Codes
FAQs
Basic Concepts
Purchase and Billing
Compatibility and Format
Connection and Network
Features
Console Operations
Database and Table
Performance and Log
Database Audit
Between TDSQL-C for MySQL and TencentDB for MySQL
Service Agreement
Service Level Agreement
Terms of Service
TDSQL-C Policy
Privacy Policy
Data Privacy and Security Agreement
General References
Standards and Certifications
Glossary
Contact Us
DocumentationTDSQL-C for MySQLProduct IntroductionRegions and AZs

Regions and AZs

PDF
Focus Mode
Font Size
Last updated: 2025-11-26 11:40:57
TencentDB data centers are hosted in multiple locations worldwide. These locations are known as regions. Each region contains multiple availability zones (AZs). Each region is an independent geographic area containing multiple isolated AZs. Separate AZs in the same region are connected via low-latency private networks. Tencent Cloud provides you with the ability to distribute Tencent Cloud resources across different locations. We recommend you place resources in different AZs to eliminate single points of failure which may lead to service unavailability.
Region name and AZ name can most directly embody the coverage of a data center. The following naming convention is used for your convenience:
A region name is composed of region + city. The region indicates the geographic area that the data center covers, while the city represents the city in or near which the data center is located.
AZ names utilize the format of city + number.

Regions

Tencent Cloud regions are completely isolated. This guarantees the maximum cross-region stability and fault tolerance. When you purchase Tencent Cloud services, we recommend you select the region closest to your end users to minimize access latency and improve download speed. Operations such as launching or viewing instances are performed at the region level. Private network communication:
Tencent Cloud resources in the same VPC within the same region under the same account can communicate with each other over private network. They can also be accessed at the private network access.
The networks of different regions are fully isolated from each other, and Tencent Cloud services in different regions cannot communicate using private networks by default.
Cloud products in different regions can communicate with each other by accessing the Internet via public IP addresses. Cloud products in different Virtual Private Clouds (VPCs) can communicate through Cloud Connect Network (CCN), which is faster and more stable.
Cloud Load Balancer currently supports intra-region traffic forwarding and being bound to CVM instances in the same region by default. If you enable the cross-region binding feature, a CLB instance can be bound to CVM instances in another region.

AZs

AZs refer to Tencent Cloud's physical data centers that are in the same region. Each AZ is independently powered and have its own network resources. They are designed to ensure that failures within one AZ can be isolated from other AZs, thereby ensuring service availability and business stability and excepting the occurrences of large-scale disasters or major power failures. Users can protect their applications from being affected by failures that occur in a single location by selecting instances in independent AZs. When launching an instance, you can select any AZ in the specified region. For high reliability, you can adopt a cross-AZ deployment solution to ensure that the service remains available when an instance in a single location fails. Examples of such solutions include CLB and EIP.

List of Regions and AZs

China

Region
AZ
South China (Guangzhou)
ap-guangzhou
Guangzhou Zone 3
ap-guangzhou-3
Guangzhou Zone 4
ap-guangzhou-4
Guangzhou Zone 6
ap-guangzhou-6
Guangzhou Zone 7
ap-guangzhou-7
Guangzhou Zone 10
ap-guangzhou-10
East China (Shanghai)
ap-shanghai
Shanghai Zone 2
ap-shanghai-2
Shanghai Zone 4
ap-shanghai-4
Shanghai Zone 5
ap-shanghai-5
Shanghai Zone 8
ap-shanghai-8
North China (Beijing)
ap-beijing
Beijing Zone 3
ap-beijing-3
Beijing Zone 5
ap-beijing-5
Beijing Zone 6
ap-beijing-6
Beijing Zone 7
ap-beijing-7
Beijing Zone 8
ap-beijing-8
North China (Beijing Finance)
ap-beijing-fsi
Beijing Finance Zone 1 (only financial institutions and enterprises can contact us to apply for activation)
ap-beijing-fsi-1
East China (Nanjing)
ap-nanjing
Nanjing Zone 1
ap-nanjing-1
Nanjing Zone 2
ap-nanjing-2
Nanjing Zone 3
ap-nanjing-3
Southwest China (Chengdu)
ap-chengdu
Chengdu Zone 1
ap-chengdu-1
Southwest China (Chongqing)
ap-chongqing
Chongqing Zone 1
ap-chongqing-1
Hong Kong/Macao/Taiwan (China Region) (Hong Kong, China)
ap-hongkong
Hong Kong Zone 1
ap-hongkong-1
Hong Kong Zone 2
ap-hongkong-2
Hong Kong Zone 3 ap-hongkong-3

Other countries and regions

Region
AZ
Southeast Asia Pacific (Singapore)
ap-singapore
Singapore Zone 2
ap-singapore-2
Singapore Zone 3
ap-singapore-3
Singapore Zone 4
ap-singapore-4
West US (Silicon Valley)
na-siliconvalley
Silicon Valley Zone 1
na-siliconvalley-1
Silicon Valley Zone 2 na-siliconvalley-2
Europe (Frankfurt)
eu-frankfurt
Frankfurt Zone 1
eu-frankfurt-1
Frankfurt Zone 2
eu-frankfurt-2
Northeast Asia (Seoul)
ap-seoul
Seoul Zone 2
ap-seoul-2
East US (Virginia)
na-ashburn
Virginia Zone 1
na-ashburn-1
Virginia Zone 2
na-ashburn-2
Northeast Asia (Tokyo)
ap-tokyo
Tokyo Zone 1
ap-tokyo-1
Tokyo Zone 2
ap-tokyo-2
Southeast Asia Pacific (Jakarta)
ap-jakarta
Jakarta Zone 1
ap-jakarta-1
Jakarta Zone 2
ap-jakarta-2
South America (São Paulo)
sa-saopaulo
São Paulo Zone 1
sa-saopaulo-1
Southeast Asia Pacific (Bangkok)
ap-bangkok
Bangkok Zone 2
ap-bangkok-2

Selection of Regions and AZs

When you purchase Tencent Cloud services, we recommend you select the region closest to your end users to minimize access latency and improve download speed.

Regions and AZs Supported by Read-Only Analysis Engine

Regions and AZs supported by the read-only analysis engine of TDSQL-C for MySQL are listed in the table below. The read-only analysis engine to be enabled and used can be in a different AZ from the read-write instance.
Region
Availability Zone
North China (Beijing)
ap-beijing
Beijing Zone 5
ap-beijing-5
Beijing Zone 6
ap-beijing-6
Beijing Zone 7
ap-beijing-7
East China (Shanghai)
ap-shanghai
Shanghai Zone 4
ap-shanghai-4
Shanghai Zone 6
ap-shanghai-6
South China (Guangzhou)
ap-guangzhou
Guangzhou Zone 4
ap-guangzhou-4
Guangzhou Zone 7
ap-guangzhou-7
Southwest China (Chengdu)
ap-chengdu
Chengdu Zone 1
ap-chengdu-1
Hong Kong (China), Macao (China), and Taiwan (China)
ap-hongkong
Hong Kong (China) Zone 2
ap-hongkong-2
East China (Nanjing)
ap-nanjing
Nanjing Zone 3
ap-nanjing-3
Southeast Asia Pacific (Singapore)
ap-singapore
Singapore Zone 4
ap-singapore-4
Eastern United States (Virginia)
na-ashburn
Virginia Zone 1
na-ashburn-1
Virginia Zone 2
na-ashburn-2
South America (São Paulo)
sa-saopaulo
São Paulo Zone 1
sa-saopaulo-1
Europe (Frankfurt)
eu-frankfurt
Frankfurt Zone 1
eu-frankfurt-1
Previous Topic: Database VersionsNext Topic: Common Concepts

Help and Support

Was this page helpful?

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

Feedback