Regions and Availability Zones

Last updated: 2021-08-09 10:53:53

    Region

    Overview

    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. We recommend that you choose the region closest to your end users to minimize access latency and improve access speed.

    The following table describes the regions, availability zones, and resource types that are currently supported by EKS.

    Characteristics

    • The networks of different regions are fully isolated. Tencent Cloud services in different regions cannot communicate via a private network by default.
    • Tencent Cloud services across regions can communicate with each other through public IPs over the Internet, while those in different VPCs can communicate with each other through CCN, which is faster and more stable.
    • Cloud Load Balancer (CLB) currently supports intra-region traffic forwarding by default. If you enable the cross-region binding feature, cross-region binding of CLB and CVM instances is supported.

    Availability Zone

    Overview

    An availability zone (AZ) is a physical IDC of Tencent Cloud with independent power supply and network in the same region. Business stability can be ensured because failures (except for major disasters or power failures) in one AZ do not affect other AZs in the same region. By starting an instance in an independent availability zone, users can protect their applications from a single point of failure.
    You can view the following table or use the DescribeZones API to get a complete AZ list.

    Characteristics

    Tencent Cloud services in the same VPC are interconnected via the private network, which means they can communicate using private IPs, even if they are in different AZs in the same region.

    Note:

    Private network interconnection refers to the interconnection of resources under the same account. Resources under different accounts are completely isolated on the private network.

    China

    Region Availability Zone
    South China (Guangzhou)
    ap-guangzhou
    Guangzhou Zone 3
    ap-guangzhou-3
    Guangzhou Zone 4
    ap-guangzhou-4
    Guangzhou Zone 6
    ap-guangzhou-6
    East China (Shanghai)
    ap-shanghai
    Shanghai Zone 2
    ap-shanghai-2
    Shanghai Zone 3
    ap-shanghai-3
    Shanghai Zone 4
    ap-shanghai-4
    Shanghai Zone 5
    ap-shanghai-5
    East China (Nanjing)
    ap-nanjing
    Nanjing Zone 1
    ap-nanjing-1
    Nanjing Zone 2
    ap-nanjing-2
    North China (Beijing)
    ap-beijing
    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
    Hong Kong, Macao and Taiwan, China (Hong Kong)
    ap-hongkong
    Hong Kong Zone 2 (Nodes in Hong Kong, China can cover services in Hong Kong/Macao/Taiwan regions)
    ap-hongkong-2

    Other Countries and Regions

    Region Availability Zone
    Southeast Asia (Singapore)
    ap-singapore
    Singapore Zone 1 (Singapore nodes can cover services in Southeast Asia)
    ap-singapore-1
    Singapore Zone 2 (Singapore nodes can cover services in Southeast Asia)
    ap-singapore-2
    Southeast Asia (Jakarta)
    ap-jakarta
    Jakarta Zone 1 (Jakarta nodes can cover services in Southeast Asia)
    ap-jakarta-1
    Northeast Asia (Seoul)
    ap-seoul
    Seoul Zone 1 (Seoul nodes can cover services in Northeast Asia)
    ap-seoul-1
    Seoul Zone 2 (Seoul nodes can cover services in Northeast Asia)
    ap-seoul-2
    Northeast Asia (Tokyo)
    ap-tokyo
    Tokyo Zone 2 (Tokyo nodes can cover services in Northeast Asia)
    ap-tokyo-2
    South Asia (Mumbai)
    ap-mumbai
    Mumbai Zone 1 (Mumbai nodes can cover services in South Asia)
    ap-mumbai-1
    Mumbai Zone 2 (Mumbai nodes can cover services in South Asia)
    ap-mumbai-2
    Southeast Asia (Bangkok)
    ap-bangkok
    Bangkok Zone 1 (Bangkok nodes can cover services in Southeast Asia)
    ap-bangkok-1
    North America (Toronto)
    na-toronto
    Toronto Zone 1 (Toronto nodes can cover services in North America)
    na-toronto-1
    Eastern US (Virginia)
    na-ashburn
    Virginia Zone 1 (Virginia nodes can cover services in Eastern US)
    na-ashburn-1
    Virginia Zone 2 (Virginia nodes can cover services in Eastern US)
    na-ashburn-2
    Europe (Frankfurt)
    eu-frankfurt
    Frankfurt Zone 1 (Frankfurt nodes can cover services in Europe)
    eu-frankfurt-1
    Europe (Moscow)
    eu-moscow
    Moscow Zone 1 (Moscow nodes can cover services in Europe)
    eu-moscow-1