- Release Notes and Announcements
- Release Notes
- Announcements
- Announcement on the Rule-Based Audit Feature for Database Audit
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Some APIs with CAM Authentication Integrated
- Notice on Elimination of Some Indicators in Event Alarms
- Commercial Billing for Database Proxy
- TencentDB for MySQL Audit Upgrade
- Added Authentication APIs
- API Authentication Upgrade
- TencentDB for MySQL API 2.0 Discontinuation
- Monitoring Module Upgrade in Shanghai Region
- Monitoring Metric Optimization
- Network Architecture Upgrade
- Change of APIs for Querying the Specifications of Purchasable Database Instances
- Replacement of Certain Old Database Proxy APIs
- Added Advanced Monitoring Metrics
- Change of Calculation Formula for Memory Utilization
- Monitoring Module Upgrade and Optimization in Guangzhou and Shanghai Regions
- Monitoring Module Upgrade
- Parameter Template and Instance Purchase Process Optimization
- Binlog Will Take up Disk Space
- User Tutorial
- Product Introduction
- Tencent Kernel TXSQL
- Overview
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Security Features
- Stability Features
- TXRocks Engine
- Purchase Guide
- Billing Overview
- Selection Guide
- Purchase Methods
- Renewal
- Payment Overdue
- Refund
- Pay-as-You-Go to Monthly Subscription
- Instance Adjustment Fee
- Backup Space Billing
- Database Audit Billing Overview
- Commercial Billing and Activity Description for Database Proxy
- Description of the Database Proxy Billing Cycle
- Viewing Bills
- Getting Started
- Database Audit
- MySQL Cluster Edition
- Operation Guide
- Use Limits
- Operation Overview
- Instance Management and Maintenance
- Instance Upgrade
- CPU Elastic Expansion
- Read-Only/Disaster Recovery Instances
- Database Proxy
- Account Management
- Database Management Center (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Data Migration
- Monitoring and Alarms
- Operation Logs
- Tag
- Practical Tutorial
- Usage Specifications of TencentDB for MySQL
- Configuring Automatic Application Reconnection
- Impact of Modifying MySQL Source Instance Parameters
- Limits on Automatic Conversion from MyISAM to InnoDB
- Creating VPCs for TencentDB for MySQL
- Enhancing Business Load Capacity with TencentDB for MySQL
- Setting up 2-Region-3-DC Disaster Recovery Architecture
- Improving TencentDB for MySQL Performance with Read/Write Separation
- Migrating Data from InnoDB to RocksDB with DTS
- Building LAMP Stack for Web Application
- Building Drupal Website
- Building All-Scenario High-Availability Architecture
- Calling MySQL APIs in Python
- White Paper
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Data Import APIs
- Rollback APIs
- Parameter APIs
- Making API Requests
- Instance APIs
- StopCpuExpand
- StartCpuExpand
- DescribeCpuExpandStrategy
- AddTimeWindow
- BalanceRoGroupLoad
- CloseWanService
- CreateRoInstanceIp
- DeleteTimeWindow
- DescribeCdbZoneConfig
- DescribeDBFeatures
- DescribeDBInstanceCharset
- DescribeDBInstanceConfig
- DescribeDBInstanceGTID
- DescribeDBInstanceInfo
- DescribeDBInstanceRebootTime
- DescribeDBSwitchRecords
- DescribeRoGroups
- DescribeRoMinScale
- DescribeTagsOfInstanceIds
- DescribeTimeWindow
- IsolateDBInstance
- ModifyAutoRenewFlag
- ModifyDBInstanceName
- ModifyDBInstanceProject
- ModifyDBInstanceVipVport
- ModifyInstanceTag
- ModifyNameOrDescByDpId
- ModifyRoGroupInfo
- ModifyTimeWindow
- OfflineIsolatedInstances
- OpenDBInstanceEncryption
- OpenDBInstanceGTID
- OpenWanService
- ReleaseIsolatedDBInstances
- RenewDBInstance
- RestartDBInstances
- StartReplication
- StopReplication
- SwitchDBInstanceMasterSlave
- SwitchDrInstanceToMaster
- SwitchForUpgrade
- UpgradeDBInstanceEngineVersion
- CreateDBInstance
- CreateDBInstanceHour
- DescribeDBInstances
- UpgradeDBInstance
- DescribeDBZoneConfig
- CreateDeployGroup
- DeleteDeployGroups
- DescribeDeployGroupList
- Database Proxy APIs
- AdjustCdbProxy
- AdjustCdbProxyAddress
- CloseCDBProxy
- CloseCdbProxyAddress
- CreateCdbProxy
- CreateCdbProxyAddress
- DescribeCdbProxyInfo
- DescribeProxyCustomConf
- DescribeProxySupportParam
- ModifyCdbProxyAddressDesc
- ModifyCdbProxyAddressVipAndVPort
- ModifyCdbProxyParam
- ReloadBalanceProxyNode
- SwitchCDBProxy
- UpgradeCDBProxyVersion
- Database Audit APIs
- Security APIs
- Task APIs
- Account APIs
- Backup APIs
- CreateBackup
- DeleteBackup
- DescribeBackupDownloadRestriction
- DescribeBackupOverview
- DescribeBackupSummaries
- DescribeBinlogBackupOverview
- DescribeDataBackupOverview
- DescribeLocalBinlogConfig
- DescribeRemoteBackupConfig
- DescribeSlowLogs
- ModifyBackupDownloadRestriction
- ModifyLocalBinlogConfig
- ModifyRemoteBackupConfig
- DescribeBackups
- DescribeBackupConfig
- DescribeBackupDecryptionKey
- DescribeBackupEncryptionStatus
- DescribeBinlogs
- ModifyBackupConfig
- ModifyBackupEncryptionStatus
- Database APIs
- Monitoring APIs
- Log-related API
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Reference
- Glossary
- Contact Us
- Preset Plugin List
- Release Notes and Announcements
- Release Notes
- Announcements
- Announcement on the Rule-Based Audit Feature for Database Audit
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Some APIs with CAM Authentication Integrated
- Notice on Elimination of Some Indicators in Event Alarms
- Commercial Billing for Database Proxy
- TencentDB for MySQL Audit Upgrade
- Added Authentication APIs
- API Authentication Upgrade
- TencentDB for MySQL API 2.0 Discontinuation
- Monitoring Module Upgrade in Shanghai Region
- Monitoring Metric Optimization
- Network Architecture Upgrade
- Change of APIs for Querying the Specifications of Purchasable Database Instances
- Replacement of Certain Old Database Proxy APIs
- Added Advanced Monitoring Metrics
- Change of Calculation Formula for Memory Utilization
- Monitoring Module Upgrade and Optimization in Guangzhou and Shanghai Regions
- Monitoring Module Upgrade
- Parameter Template and Instance Purchase Process Optimization
- Binlog Will Take up Disk Space
- User Tutorial
- Product Introduction
- Tencent Kernel TXSQL
- Overview
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Security Features
- Stability Features
- TXRocks Engine
- Purchase Guide
- Billing Overview
- Selection Guide
- Purchase Methods
- Renewal
- Payment Overdue
- Refund
- Pay-as-You-Go to Monthly Subscription
- Instance Adjustment Fee
- Backup Space Billing
- Database Audit Billing Overview
- Commercial Billing and Activity Description for Database Proxy
- Description of the Database Proxy Billing Cycle
- Viewing Bills
- Getting Started
- Database Audit
- MySQL Cluster Edition
- Operation Guide
- Use Limits
- Operation Overview
- Instance Management and Maintenance
- Instance Upgrade
- CPU Elastic Expansion
- Read-Only/Disaster Recovery Instances
- Database Proxy
- Account Management
- Database Management Center (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Data Migration
- Monitoring and Alarms
- Operation Logs
- Tag
- Practical Tutorial
- Usage Specifications of TencentDB for MySQL
- Configuring Automatic Application Reconnection
- Impact of Modifying MySQL Source Instance Parameters
- Limits on Automatic Conversion from MyISAM to InnoDB
- Creating VPCs for TencentDB for MySQL
- Enhancing Business Load Capacity with TencentDB for MySQL
- Setting up 2-Region-3-DC Disaster Recovery Architecture
- Improving TencentDB for MySQL Performance with Read/Write Separation
- Migrating Data from InnoDB to RocksDB with DTS
- Building LAMP Stack for Web Application
- Building Drupal Website
- Building All-Scenario High-Availability Architecture
- Calling MySQL APIs in Python
- White Paper
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Data Import APIs
- Rollback APIs
- Parameter APIs
- Making API Requests
- Instance APIs
- StopCpuExpand
- StartCpuExpand
- DescribeCpuExpandStrategy
- AddTimeWindow
- BalanceRoGroupLoad
- CloseWanService
- CreateRoInstanceIp
- DeleteTimeWindow
- DescribeCdbZoneConfig
- DescribeDBFeatures
- DescribeDBInstanceCharset
- DescribeDBInstanceConfig
- DescribeDBInstanceGTID
- DescribeDBInstanceInfo
- DescribeDBInstanceRebootTime
- DescribeDBSwitchRecords
- DescribeRoGroups
- DescribeRoMinScale
- DescribeTagsOfInstanceIds
- DescribeTimeWindow
- IsolateDBInstance
- ModifyAutoRenewFlag
- ModifyDBInstanceName
- ModifyDBInstanceProject
- ModifyDBInstanceVipVport
- ModifyInstanceTag
- ModifyNameOrDescByDpId
- ModifyRoGroupInfo
- ModifyTimeWindow
- OfflineIsolatedInstances
- OpenDBInstanceEncryption
- OpenDBInstanceGTID
- OpenWanService
- ReleaseIsolatedDBInstances
- RenewDBInstance
- RestartDBInstances
- StartReplication
- StopReplication
- SwitchDBInstanceMasterSlave
- SwitchDrInstanceToMaster
- SwitchForUpgrade
- UpgradeDBInstanceEngineVersion
- CreateDBInstance
- CreateDBInstanceHour
- DescribeDBInstances
- UpgradeDBInstance
- DescribeDBZoneConfig
- CreateDeployGroup
- DeleteDeployGroups
- DescribeDeployGroupList
- Database Proxy APIs
- AdjustCdbProxy
- AdjustCdbProxyAddress
- CloseCDBProxy
- CloseCdbProxyAddress
- CreateCdbProxy
- CreateCdbProxyAddress
- DescribeCdbProxyInfo
- DescribeProxyCustomConf
- DescribeProxySupportParam
- ModifyCdbProxyAddressDesc
- ModifyCdbProxyAddressVipAndVPort
- ModifyCdbProxyParam
- ReloadBalanceProxyNode
- SwitchCDBProxy
- UpgradeCDBProxyVersion
- Database Audit APIs
- Security APIs
- Task APIs
- Account APIs
- Backup APIs
- CreateBackup
- DeleteBackup
- DescribeBackupDownloadRestriction
- DescribeBackupOverview
- DescribeBackupSummaries
- DescribeBinlogBackupOverview
- DescribeDataBackupOverview
- DescribeLocalBinlogConfig
- DescribeRemoteBackupConfig
- DescribeSlowLogs
- ModifyBackupDownloadRestriction
- ModifyLocalBinlogConfig
- ModifyRemoteBackupConfig
- DescribeBackups
- DescribeBackupConfig
- DescribeBackupDecryptionKey
- DescribeBackupEncryptionStatus
- DescribeBinlogs
- ModifyBackupConfig
- ModifyBackupEncryptionStatus
- Database APIs
- Monitoring APIs
- Log-related API
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Reference
- Glossary
- Contact Us
- Preset Plugin List
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 with multiple isolated AZs. Separate AZs in the same region are connected via low-latency private networks. Tencent Cloud allows you 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.
Tencent Cloud services across regions can communicate with each other through public IPs as instructed in Internet Access, while those in different VPCs can communicate with each other through Cloud Connect Network that is faster and steadier.
Cloud Load Balancer (CLB) currently supports intra-region traffic forwarding by default. If cross-region binding is enabled, cross-region binding of CLB and CVM instances is supported.
AZs
An availability zone (AZ) is a physical IDC of Tencent Cloud with independent power supply and network in the same region. It can ensure business stability, as failures (except for major disasters or power failures) in one AZ are isolated without affecting other AZs in the same region. By starting an instance in an independent AZ, users can protect their applications from being affected by a single point of failure.
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 Cloud Load Balancer and Elastic IP (EIP).
List of Regions and AZs
The supported regions and AZs are as follows:
Note:
Currently, public network access is supported only in the following regions:
Guangzhou, Shanghai, Nanjing, Beijing, Chengdu, Chongqing, Hong Kong (China), Singapore, Seoul, Tokyo, Silicon Valley, and Frankfurt
China
Region | AZ |
South China (Guangzhou)ap-guangzhou | Guangzhou Zone 1 (sold out) ap-guangzhou-1 |
| Guangzhou Zone 2 (sold out) ap-guangzhou-2 |
| Guangzhou Zone 3 ap-guangzhou-3 |
| Guangzhou Zone 4 ap-guangzhou-4 |
| Guangzhou Zone 6 ap-guangzhou-6 |
| Guangzhou Zone 7 ap-guangzhou-7 |
South China (Shenzhen Finance)ap-shenzhen-fsi | Shenzhen Finance Zone 1 (only financial institutions and enterprises can contact us to apply for activation)ap-shenzhen-fsi-1 |
| Shenzhen Finance Zone 2(only financial institutions and enterprises can contact us to apply for activation)ap-shenzhen-fsi-2 |
| Shenzhen Finance Zone 3(only financial institutions and enterprises can contact us to apply for activation)ap-shenzhen-fsi-3 |
East China (Shanghai)ap-shanghai | Shanghai Zone 1ap-shanghai-1 |
| Shanghai Zone 2ap-shanghai-2 |
| Shanghai Zone 3ap-shanghai-3 |
| Shanghai Zone 4ap-shanghai-4 |
| Shanghai Zone 5ap-shanghai-5 |
| Shanghai Zone 8ap-shanghai-8 |
East China (Nanjing)ap-nanjing | Nanjing Zone 1ap-nanjing-1 |
| Nanjing Zone 2ap-nanjing-2 |
| Nanjing Zone 3ap-nanjing-3 |
East China (Shanghai Finance)ap-shanghai-fsi | Shanghai Finance Zone 1 (only financial institutions and enterprises can contact us to apply for activation)ap-shanghai-fsi-1 |
| Shanghai Finance Zone 2 (only financial institutions and enterprises can contact us to apply for activation)ap-shanghai-fsi-2 |
| Shanghai Finance Zone 3 (only financial institutions and enterprises can contact us to apply for activation)ap-shanghai-fsi-3 |
North China (Beijing)ap-beijing | Beijing Zone 1ap-beijing-1 |
| Beijing Zone 2ap-beijing-2 |
| Beijing Zone 3ap-beijing-3 |
| Beijing Zone 4ap-beijing-4 |
| Beijing Zone 5ap-beijing-5 |
| Beijing Zone 6ap-beijing-6 |
| Beijing Zone 7ap-beijing-7 |
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 |
Southwest China (Chengdu)ap-chengdu | Chengdu Zone 1ap-chengdu-1 |
| Chengdu Zone 2ap-chengdu-2 |
Southwest China (Chongqing)ap-chongqing | Chongqing Zone 1ap-chongqing-1 |
Hong Kong/Macao/Taiwan (Hong Kong, China)ap-hongkong | Hong Kong Zone 1 (Hong Kong nodes cover services in the China regions of Hong Kong, Macao, and Taiwan)ap-hongkong-1 |
| Hong Kong Zone 2 (Hong Kong nodes cover services in the China regions of Hong Kong, Macao, and Taiwan)ap-hongkong-2 |
| Hong Kong Zone 3 (Hong Kong nodes cover services in the China regions of Hong Kong, Macao, and Taiwan)ap-hongkong-3 |
Other countries and regions
Region | AZ |
Southeast Asia (Singapore)ap-singapore | Singapore Zone 1 (Singapore nodes cover services in Southeast Asia)ap-singapore-1 |
| Singapore Zone 2 (Singapore nodes cover services in Southeast Asia)ap-singapore-2 |
| Singapore Zone 3 (Singapore nodes cover services in Southeast Asia)ap-singapore-3 |
| Singapore Zone 4 (Singapore nodes cover services in Southeast Asia)ap-singapore-4 |
Southeast Asia (Jakarta)ap-jakarta | Jakarta Zone 1ap-jakarta-1 |
| Jakarta Zone 2ap-jakarta-2 |
Southeast Asia (Bangkok)ap-bangkok | Bangkok Zone 1 (Bangkok nodes cover services in Southeast Asia)ap-bangkok-1 |
| Bangkok Zone 2 (Bangkok nodes cover services in Southeast Asia)ap-bangkok-2 |
South Asia (Mumbai)ap-mumbai | Mumbai Zone 1 (Mumbai nodes cover services in South Asia)ap-mumbai-1 |
| Mumbai Zone 2 (Mumbai nodes cover services in South Asia)ap-mumbai-2 |
Northeast Asia (Seoul)ap-seoul | Seoul Zone 1 (Seoul nodes cover services in Northeast Asia)ap-seoul-1 |
| Seoul Zone 2 (Seoul nodes cover services in Northeast Asia)ap-seoul-2 |
Northeast Asia (Tokyo)ap-tokyo | Tokyo Zone 1 (Tokyo nodes cover services in Northeast Asia)ap-tokyo-1 |
| Tokyo Zone 2 (Tokyo nodes cover services in Northeast Asia)ap-tokyo-2 |
US West (Silicon Valley)na-siliconvalley | Silicon Valley Zone 1 (sold out)na-siliconvalley-1 |
| Silicon Valley Zone 2 (Silicon Valley nodes cover services in Western US)na-siliconvalley-2 |
US East (Virginia)na-ashburn | Virginia Zone 1 (Virginia nodes cover services in Eastern US)na-ashburn-1 |
| Virginia Zone 2 (Virginia nodes cover services in Eastern US)na-ashburn-2 |
South America (São Paulo)sa-saopaulo | São Paulo Zone 1 (São Paulo nodes cover services in South America)sa-saopaulo-1 |
Europe (Frankfurt)eu-frankfurt | Frankfurt Zone 1 (Frankfurt nodes cover services in Europe)eu-frankfurt-1 |
| Frankfurt Zone 2 (Frankfurt nodes cover services in Europe)eu-frankfurt-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.
Yes
No
Was this page helpful?