tencent cloud

Feedback

Regions and Availability Zones

Last updated: 2023-03-30 16:26:40

    Regions

    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. When purchasing Tencent Cloud services, we recommend selecting the region closest to your end users to minimize access latency and improve download speed.
    You can see the table below for the regions, availability zones and resource types currently supported by TKE Serverless cluster. Other regions will be opened gradually.

    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 in different regions can communicate with each other through public IP addresses over the Internet, while those in different VPCs can communicate with each other through CCN, which is faster and more stable.
    Cloud Load Balancer currently supports intra-region traffic forwarding, and binding of CVMs in the same region. If the cross-region binding function is enabled, then binding CVMs to the Cloud Load Balancer across regions is supported.

    AZs

    Overview

    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. You can view the following table or use the DescribeZones API to view the complete list of AZs.

    Characteristics

    Tencent Cloud products that are in the same region, different AZs, and the same VPC are interconnected through the private network. They can be accessed directly through private IP addresses.
    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.

    AZs Supported by TKE Serverless Clusters

    China

    Region(s)
    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
    Guangzhou Zone 7
    ap-guangzhou-7
    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 (Chengdu)
    ap-chengdu
    Chengdu Zone 1
    ap-chengdu-1
    Chengdu Zone 2
    ap-chengdu-2
    Hong Kong/Macao/Taiwan (China Region) (Hong Kong, China)
    ap-hongkong
    Hong Kong Zone 2 (Hong Kong nodes can cover services in the China regions of Hong Kong, Macao, and Taiwan)
    ap-hongkong-2

    Other countries and regions

    Region(s)
    Availability Zone
    Southeast Asia Pacific (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
    Southeast Asia (Jakarta)
    ap-jakarta
    Jakarta Zone 1 (Jakarta nodes cover services in Southeast Asia)
    ap-jakarta-1
    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 2 (Tokyo node AZs cover services in Northeast Asia)
    ap-tokyo-2
    Southern Asia Pacific (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
    Southeast Asia Pacific (Bangkok)
    ap-bangkok
    Bangkok Zone 1 (Bangkok node users cover services in Southeast Asia)
    ap-bangkok-1
    North America (Toronto)
    na-toronto
    Toronto Zone 1 (Toronto nodes cover services in North America)
    na-toronto-1
    East US (Virginia)
    na-ashburn
    Virginia Zone 1 (Virginia node users cover services in East US)
    na-ashburn-1
    Virginia Zone 2 (Virginia node users cover services in East US)
    na-ashburn-2
    Europe Zone (Frankfurt)
    eu-frankfurt
    Frankfurt Zone 1 (Frankfurt nodes cover services in Europe)
    eu-frankfurt-1
    
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support