- User Guide
- Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Operation Overview
- Usage Limits
- Creating Cloud Disks
- Attaching Cloud Disks
- Initializing Cloud Disks
- Expanding Cloud Disks
- Overview
- Expanding Cloud Disks
- Extending System Disk Partitions and File Systems Online
- Extending Data Disk Partitions and File Systems (Windows)
- Extending Data Disk Partitions and File Systems (Linux)
- Detaching Cloud Disks
- Viewing Cloud Disk Information
- Terminating Cloud Disks
- Adjusting Cloud Disk Performance
- Cloud Disk Data Protection Configuration
- Cloud Disk Data Backup Point
- Managing Snapshots
- Monitoring and Alarms
- Best Practices
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Snapshot APIs
- ApplySnapshot
- DeleteSnapshots
- DescribeSnapshots
- CreateSnapshot
- ModifySnapshotAttribute
- UnbindAutoSnapshotPolicy
- DescribeDiskAssociatedAutoSnapshotPolicy
- DescribeAutoSnapshotPolicies
- DeleteAutoSnapshotPolicies
- CreateAutoSnapshotPolicy
- BindAutoSnapshotPolicy
- ModifyAutoSnapshotPolicyAttribute
- ModifySnapshotsSharePermission
- DescribeSnapshotSharePermission
- GetSnapOverview
- CopySnapshotCrossRegions
- Cloud Disk APIs
- CreateDiskBackup
- ModifyDiskAttributes
- ResizeDisk
- DescribeInstancesDiskNum
- CreateDisks
- AttachDisks
- InquiryPriceCreateDisks
- DescribeDisks
- DetachDisks
- DescribeDiskConfigQuota
- InquiryPriceResizeDisk
- TerminateDisks
- ModifyDiskExtraPerformance
- InquirePriceModifyDiskExtraPerformance
- InitializeDisks
- ModifyDiskBackupQuota
- InquirePriceModifyDiskBackupQuota
- DescribeDiskBackups
- DeleteDiskBackups
- ApplyDiskBackup
- Data Types
- Error Codes
- FAQs
- Cross-region Replication
- CBS Service Level Agreement
- Contact Us
- Glossary
- User Guide
- Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Operation Overview
- Usage Limits
- Creating Cloud Disks
- Attaching Cloud Disks
- Initializing Cloud Disks
- Expanding Cloud Disks
- Overview
- Expanding Cloud Disks
- Extending System Disk Partitions and File Systems Online
- Extending Data Disk Partitions and File Systems (Windows)
- Extending Data Disk Partitions and File Systems (Linux)
- Detaching Cloud Disks
- Viewing Cloud Disk Information
- Terminating Cloud Disks
- Adjusting Cloud Disk Performance
- Cloud Disk Data Protection Configuration
- Cloud Disk Data Backup Point
- Managing Snapshots
- Monitoring and Alarms
- Best Practices
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Snapshot APIs
- ApplySnapshot
- DeleteSnapshots
- DescribeSnapshots
- CreateSnapshot
- ModifySnapshotAttribute
- UnbindAutoSnapshotPolicy
- DescribeDiskAssociatedAutoSnapshotPolicy
- DescribeAutoSnapshotPolicies
- DeleteAutoSnapshotPolicies
- CreateAutoSnapshotPolicy
- BindAutoSnapshotPolicy
- ModifyAutoSnapshotPolicyAttribute
- ModifySnapshotsSharePermission
- DescribeSnapshotSharePermission
- GetSnapOverview
- CopySnapshotCrossRegions
- Cloud Disk APIs
- CreateDiskBackup
- ModifyDiskAttributes
- ResizeDisk
- DescribeInstancesDiskNum
- CreateDisks
- AttachDisks
- InquiryPriceCreateDisks
- DescribeDisks
- DetachDisks
- DescribeDiskConfigQuota
- InquiryPriceResizeDisk
- TerminateDisks
- ModifyDiskExtraPerformance
- InquirePriceModifyDiskExtraPerformance
- InitializeDisks
- ModifyDiskBackupQuota
- InquirePriceModifyDiskBackupQuota
- DescribeDiskBackups
- DeleteDiskBackups
- ApplyDiskBackup
- Data Types
- Error Codes
- FAQs
- Cross-region Replication
- CBS Service Level Agreement
- Contact Us
- Glossary
Regions
A region is the physical location of an IDC. In Tencent Cloud, regions are fully isolated from each other, ensuring cross-region stability and fault tolerance. When purchasing Tencent Cloud services, we recommend selecting the region closest to your end users to minimize access latency and improve download speed.
Regions have the following characteristics:
The networks of different regions are fully isolated. Tencent Cloud services in different regions cannot communicate via a private network by default.
Cloud products in different regions can access the Internet through the public network service. Cloud products in a VPC can also use Tencent Cloud's Peering Connection to communicate with each other by using Tencent Cloud's high-speed network to implement a connection that is faster and more stable than Internet access.
Cloud Load Balancer currently supports intra-region traffic forwarding by default. If you enable the cross-region binding feature, a CLB instance can be bound to CVM instances in another region.
Availability Zones
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.
Availability zones have the following characteristics:
For cloud products under the same Tencent Cloud account, products in the same region but different availability zones and under the same VPC can communicate with each other through the private network, and the private network service can be used for direct access.
Resources under different Tencent Cloud accounts are availability zone-specific, meaning they cannot communicate via a private network, even if they are in the same region.
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 |
East China (Shanghai)ap-shanghai | Shanghai Zone 1 (sold out) ap-shanghai-1 |
| Shanghai Zone 2 ap-shanghai-2 |
| Shanghai Zone 3 ap-shanghai-3 |
| Shanghai Zone 4 ap-shanghai-4 |
| Shanghai Zone 5 ap-shanghai-5 |
| Shanghai Zone 8 ap-shanghai-8 |
East China (Nanjing)ap-nanjing | Nanjing Zone 1 ap-nanjing-1 |
| Nanjing Zone 2 ap-nanjing-2 |
| Nanjing Zone 3 ap-nanjing-3 |
North China (Beijing)ap-beijing | Beijing Zone 1 (sold out) ap-beijing-1 |
| Beijing Zone 2 ap-beijing-2 |
| Beijing Zone 3 ap-beijing-3 |
| Beijing Zone 4 ap-beijing-4 |
| Beijing Zone 5 ap-beijing-5 |
| Beijing Zone 6 ap-beijing-6 |
| Beijing Zone 7 ap-beijing-7 |
Southwest China (Chengdu)ap-chengdu | Chengdu Zone 1 ap-chengdu-1 |
| Chengdu Zone 2 ap-chengdu-2 |
Southwest China (Chongqing)ap-chongqing | Chongqing Zone 1 ap-chongqing-1 |
Hong Kong/Macao/Taiwan (Hong Kong, China)ap-hongkong | Hong Kong Zone 1 (Nodes in Hong Kong, China can cover Hong Kong/Macao/Taiwan regions) (sold out) ap-hongkong-1 |
| Hong Kong Zone 2 (Nodes in Hong Kong, China can cover Hong Kong/Macao/Taiwan regions) ap-hongkong-2 |
| Hong Kong Zone 3 (Nodes in Hong Kong, China can cover Hong Kong/Macao/Taiwan regions) ap-hongkong-3 |
Note:
The product is in beta test for Jinan, Hangzhou, Fuzhou, Wuhan, Changsha, and Shijiazhuang regions. To try it out, submit a ticket for application.
Other Countries and Regions
Region | AZ |
Southeast Asia (Singapore) ap-singapore | Singapore Zone 1 (Nodes in Singapore can cover Southeast Asia) ap-singapore-1 |
| Singapore Zone 2 (Nodes in Singapore can cover Southeast Asia) ap-singapore-2 |
| Singapore Zone 3 (Nodes in Singapore can cover Southeast Asia) ap-singapore-3 |
| Singapore Zone 4 (Nodes in Singapore can cover Southeast Asia) ap-singapore-4 |
Southeast Asia (Jakarta) ap-jakarta | Jakarta Zone 1 (Nodes in Jakarta can cover Southeast Asia) ap-jakarta-1 |
| Jakarta Zone 2 (Nodes in Jakarta can cover Southeast Asia) ap-jakarta-2 |
Northeast Asia (Seoul) ap-seoul | Seoul Zone 1 (Nodes in Seoul can cover Northeast Asia) ap-seoul-1 |
| Seoul Zone 2 (Nodes in Seoul can cover Northeast Asia) ap-seoul-2 |
Northeast Asia (Tokyo) ap-tokyo | Tokyo Zone 1 (Nodes in Tokyo can cover Northeast Asia) ap-tokyo-1 |
| Tokyo Zone 2 (Tokyo nodes can cover services in Northeast Asia) ap-tokyo-2 |
South Asia (Mumbai) ap-mumbai | Mumbai Zone 1 (Nodes in Mumbai can cover South Asia) ap-mumbai-1 |
| Mumbai Zone 2 (Nodes in Mumbai can cover South Asia) ap-mumbai-2 |
Southeast Asia (Bangkok) ap-bangkok | Bangkok Zone 1 (Nodes in Bangkok can cover Southeast Asia) ap-bangkok-1 |
| Bangkok Zone 2 (Nodes in Bangkok can cover Southeast Asia) ap-bangkok-2 |
North America (Toronto) na-toronto | Toronto Zone 1 (Nodes in Toronto can cover North America) na-toronto-1 |
South America (São Paulo) sa-saopaulo | Sao Paulo Zone 1 (Sao Paulo nodes cover services in South America) sa-saopaulo-1 |
Western US (Silicon Valley) na-siliconvalley | Silicon Valley Zone 1 (Nodes in Silicon Valley can cover Western US) na-siliconvalley-1 |
| Silicon Valley Zone 2 (Nodes in Silicon Valley can cover Western US) na-siliconvalley-2 |
Eastern US (Virginia) na-ashburn | Virginia Zone 1 (Nodes in Virginia can cover Eastern US) na-ashburn-1 |
| Virginia Zone 2 (Nodes in Virginia can cover Eastern US) na-ashburn-2 |
Europe (Frankfurt) eu-frankfurt | Frankfurt Zone 1 (Nodes in Frankfurt can cover Europe) eu-frankfurt-1 |
| Frankfurt Zone 2 (Nodes in Frankfurt can cover Europe) eu-frankfurt-2 |
Europe (Moscow) eu-moscow | Northeast Europe Zone 1 (Nodes in Moscow can cover Europe) eu-moscow-1 |
Selection of Regions and AZs
When selecting a region and availability zone, take the following into consideration:
A cloud disk can only be attached to a CVM in the same availability zone.
The region of the CVM on which the cloud disk will be used, your location, and the location of your users. We recommend that you choose the region closest to your end users when purchasing Tencent Cloud services to minimize access latency and improve access speed.
The relationship between the CVM on which the cloud disk will be used and other Tencent Cloud services. When you select other Tencent Cloud services, we recommend you try to locate them all in the same availability zone of a single region to allow them to communicate with each other through the private network, reducing access latency and increasing access speed.
High availability and disaster recovery. Even if you have just one VPC, we still recommend that you deploy your businesses in different availability zones to prevent a single point of failure and enable cross-AZ disaster recovery.
There may be network latency among different AZs. We recommend you assess your business requirements and find the optimal balance between high availability and low latency.
Related Operations
Actions such as the use and viewing of cloud disks are region-specific. To easily migrate data and services to other regions or construct a cross-region disaster recovery system, you can copy snapshots to other regions. For more information, see Cross-region Snapshot Replicating.
Yes
No
Was this page helpful?