A region refers to the geographical area of physical data centers. Availability zones are physically independent data centers within the same Tencent Cloud region, with separate power and network resources. For more information, see CVM - Regions and AZs. Supported Regions
China
|
South China | Guangzhou | ap-guangzhou | ✓ | ✓ | ✓ | ✓ |
| Qingyuan | ap-qingyuan | × | ✓ | ✓ | × |
| Shenzhen Finance | ap-shenzhen-fsi | ✓ | × | × | × |
East China | Nanjing | ap-nanjing | ✓ | ✓ | ✓ | ✓ |
| Shanghai | ap-shanghai | ✓ | ✓ | ✓ | ✓ |
| Shanghai Finance | ap-shanghai-fsi | ✓ | ✓ | ✓ | ✓ |
| Shanghai Autonomous Driving Cloud | ap-shanghai-adc | ✓ | ✓ | ✓ | ✓ |
Hong Kong (China), Macao (China), and Taiwan (China) | Hong Kong (China) | ap-hongkong | ✓ | ✓ | ✓ | ✓ |
North China | Beijing | ap-beijing | ✓ | ✓ | ✓ | ✓ |
| Beijing Finance | ap-beijing-fsi | × | × | × | ✓ |
Southwest China | Chengdu | ap-chengdu | ✓ | × | × | × |
| Chongqing | ap-chongqing | ✓ | ✓ | × | × |
Other Countries and Regions
|
Southeast Asia | Singapore | ap-singapore | ✓ | ✓ | ✓ | ✓ |
| Bangkok | ap-bangkok | ✓ | × | × | × |
| Jakarta | ap-jakarta | ✓ | × | ✓ | ✓ |
Northeast Asia | Seoul | ap-seoul | ✓ | × | × | ✓ |
| Tokyo | ap-tokyo | ✓ | × | × | ✓ |
Western United States | Silicon Valley | na-siliconvalley | ✓ | ✓ | ✓ | ✓ |
Eastern United States | Virginia | na-ashburn | ✓ | ✓ | ✓ | ✓ |
Europe | Frankfurt | eu-frankfurt | ✓ | × | × | ✓ |
South America | São Paulo | sa-saopaulo | ✓ | × | × | × |
If the above regions do not meet your requirements, you can submit a ticket to request enabling new regions and availability zones. How to Select a Region and an AZ
When you select a region and an availability zone (AZ), you should consider the following factors:
The region of your TDMQ for RocketMQ cluster, your own location, and the location of your target users. We recommend that you select the region closest to your customers when you purchase a TDMQ for RocketMQ cluster to reduce access latency and improve access speed.
The relationship between TDMQ for RocketMQ and other cloud products. We recommend that you deploy other cloud products in the same region and availability zone whenever possible. This allows different cloud products to communicate over the private network, reducing access latency and improving access speed.
High availability and disaster recovery considerations for your business. Even in scenarios with only one Virtual Private Cloud (VPC), we recommend that you deploy your business across at least two different availability zones to ensure fault isolation between availability zones and achieve cross-zone disaster recovery.
Possible network communication latency between availability zones. Evaluate it based on your actual business requirements to find the optimal balance between high availability and low latency.