Regions and Availability Zones

Last updated: 2020-03-13 12:09:01

    Data centers hosted by Tencent Cloud are distributed at multiple locations around the globe. The locations of these nodes are referred to as regions, and each region comprises multiple availability zones.
    When creating a VPC, you need to select a region. When creating a subnet, you need to select an availability zone, and subnets must be in the region where the VPC resides. Understanding basic information regarding regions and availability zones helps you better deploy resources in the cloud.

    Regions

    Tencent Cloud regions are named after the rule of coverage range + city where the data center is located, for example, South China (Guangzhou), East China (Shanghai), and Asia Pacific (Seoul). The coverage range indicates the coverage of the data center. The city indicates the city where the data center is located or the closest city. For the list of regions, see the [List of Tencent Cloud regions and availability zones] (#liebiao).
    Region features:

    • A VPC has the region attribute, and each VPC belongs to only one region.
    • Whether in the same region or different regions, different VPC instances are isolated from each other and cannot directly communicate through the private network. If communication between VPC instances is needed, you can use CCN or peering connections.

    Availability Zones

    Availability zones refer to Tencent Cloud’s physical data centers with power facilities and networks that are independent of each other within the same region. Each region has at least one availability zone. In the following example, four availability zones exist in the Guangzhou region.
    Establishing multiple availability zones in one region is a way to implement failure isolation between availability zones (with the exception of large-scale disasters or large-scale power outages) so that failures do not spread and users’ businesses are not interrupted.

    Availability zone features:

    • A subnet of a VPC is associated with an availability zone, and one VPC can concurrently host subnets in different availability zones (for example, the VPC in the Guangzhou region can host subnets in Zone 1, Zone 2, Zone 3, and Zone 4 of the Guangzhou region.)
    • Cloud products in the same region and same VPC can interconnect with each other even if they are in different availability zones. For example, subnets in different availability zones of the VPC in the Guangzhou region can directly interconnect with each other through the private network via private IP addresses.
    • Resources of different accounts are completely isolated from each other on private networks. You must establish cross-account peering connections to achieve the interconnection of these resources.

    Choosing Regions and Availability Zones

    When choosing regions and availability zones, you must take the following into consideration:

    • The region of the CVM and the geographical locations of you and your target users: we recommend that you select the region closest to your end users to reduce access latency and increase the access speed.
    • Relationships between the CVM and other cloud products: we recommend that the selected cloud products reside in the same availability zone of the same region to facilitate interconnection through private networks and to reduce access latency and increase the access speed.
    • High availability of services and disaster recovery concerns: even in scenarios with a single VPC, we recommend that you deploy services in different availability zones to guarantee failure isolation between availability zones and to achieve cross-zone disaster recovery.
    • Network communication delay may occur between availability zones, and therefore it is necessary to make an assessment based on the actual requirements of services to figure out the optimal balance point between high availability and low latency.

    Migrating an Instance to Another Availability Zone

    You cannot change the availability zone of an instance that has been launched, but can migrate the instance to another availability zone and keep the current private IP address. The detailed process is as follows:

    • Create a custom image from the original instance.
    • Use the custom image to launch an instance in the target availability zone.
    • Update the configuration of the new instance.

    For more detailed steps, see Migrating an Instance to Another Availability Zone.

    List of Tencent Cloud Regions and Availability Zones

    China

    Region Availability Zone
    South China (Guangzhou)
    ap-guangzhou
    Guangzhou Zone 1 (sold out)
    ap-guangzhou-1
    Guangzhou Zone 2
    ap-guangzhou-2
    Guangzhou Zone 3
    ap-guangzhou-3
    Guangzhou Zone 4
    ap-guangzhou-4
    South China (Shenzhen Finance)
    ap-shenzhen-fsi
    Shenzhen Finance Zone 1(only for financial institutions and enterprises, and you must submit a ticket to apply for activation)
    ap-shenzhen-fsi-1
    Shenzhen Finance Zone 2(only for financial institutions and enterprises, and you must submit a ticket to apply for activation)
    ap-shenzhen-fsi-2
    Shenzhen Finance Zone 3(only for financial institutions and enterprises, and you must submit a ticket to apply for activation)
    ap-shenzhen-fsi-3
    East China (Shanghai)
    ap-shanghai
    Shanghai Zone 1
    ap-shanghai-1
    Shanghai Zone 2
    ap-shanghai-2
    Shanghai Zone 3
    ap-shanghai-3
    Shanghai Zone 4
    ap-shanghai-4
    East China (Shanghai Finance)
    ap-shanghai-fsi
    Shanghai Finance Zone 1 (only for financial institutions and enterprises, and you must submit a ticket to apply for activation)
    ap-shanghai-fsi-1
    Shanghai Finance Zone 2 (only for financial institutions and enterprises, and you must submit a ticket to apply for activation)
    ap-shanghai-fsi-2
    Shanghai Finance Zone 3 (only for financial institutions and enterprises, and you must submit a ticket to apply for activation)
    ap-shanghai-fsi-3
    East China (Nanjing)
    ap-nanjing
    Nanjing Zone 1
    ap-nanjing-1
    Nanjing Zone 2
    ap-nanjing-2
    North China (Beijing)
    ap-beijing
    Beijing Zone 1
    ap-beijing-1
    Beijing Zone 2
    ap-beijing-2
    Beijing Zone 3
    ap-beijing-3
    Beijing Zone 4
    ap-beijing-4
    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 (China), Macao (China), and Taiwan (China) (Hong Kong, China)
    ap-hongkong
    Hong Kong (China) Zone 1 (nodes in the Hong Kong (China) region can be used to cover Hong Kong (China), Macao (China), and Taiwan (China))
    ap-hongkong-1
    Hong Kong (China) Zone 2 (nodes in the Hong Kong (China) region can be used to cover Hong Kong (China), Macao (China), and Taiwan (China))
    ap-hongkong-2

    Other Regions

    Region Availability Zone
    Southeast Asia Pacific (Singapore)
    ap-singapore
    Singapore Zone 1 (Singapore nodes can be used to cover Southeast Asia Pacific)
    ap-singapore-1
    Northeast Asia Pacific (Seoul)
    ap-seoul
    Seoul Zone 1 (Seoul nodes can be used to cover Northeast Asia Pacific)
    ap-seoul-1
    Northeast Asia Pacific (Tokyo)
    ap-tokyo
    Tokyo Zone 1 (Tokyo nodes can be used to cover Northeast Asia Pacific)
    ap-tokyo-1
    Southern Asia Pacific (Mumbai)
    ap-mumbai
    Mumbai Zone 1 (Mumbai nodes can be used to cover Southern Asia Pacific)
    ap-mumbai-1
    Southeast Asia Pacific (Bangkok)
    ap-bangkok
    Bangkok Zone 1 (Bangkok nodes can be used to cover Southeast Asia Pacific)
    ap-bangkok-1
    North America (Toronto)
    na-toronto
    Toronto Zone 1 (Toronto nodes can be used to cover North America)
    na-toronto-1
    Western US (Silicon Valley)
    na-siliconvalley
    Silicon Valley Zone 1 (Silicon Valley nodes can be used to cover Western US)
    na-siliconvalley-1
    Silicon Valley Zone 2 (Silicon Valley nodes can be used to cover Western US)
    na-siliconvalley-2
    Eastern US (Virginia)
    na-ashburn
    Virginia Zone 1 (Virginia nodes can be used to cover Eastern US)
    na-ashburn-1
    Europe (Frankfurt)
    eu-frankfurt
    Frankfurt Zone 1 (Frankfurt nodes can be used to cover Europe)
    eu-frankfurt-1
    Europe (Moscow)
    eu-moscow
    Moscow Zone 1 (Moscow nodes can be used to cover Europe)
    eu-moscow-1

    Was this page helpful?

    Was this page helpful?

    • Not at all
    • Not very helpful
    • Somewhat helpful
    • Very helpful
    • Extremely helpful
    Send Feedback
    Help