Alibaba Cloud Ping Test
Find your closest, lowest-latency Alibaba Cloud region. Aliyun ping test from your browser. Measures the public-facing OSS path to every Alibaba Cloud region.
29 Alibaba Cloud regions measured · browser-based · no signup
29regions
- Alibaba CloudJapan (Tokyo)ap-northeast-1Tokyo, JP—
- Alibaba CloudSouth Korea (Seoul)ap-northeast-2Seoul, KR—
- Alibaba CloudSingaporeap-southeast-1Singapore, SG—
- Alibaba CloudMalaysia (Kuala Lumpur)ap-southeast-3Kuala Lumpur, MY—
- Alibaba CloudIndonesia (Jakarta)ap-southeast-5Jakarta, ID—
- Alibaba CloudPhilippines (Manila)ap-southeast-6Manila, PH—
- Alibaba CloudThailand (Bangkok)ap-southeast-7Bangkok, TH—
- Alibaba CloudChina (Beijing)cn-beijingBeijing, CN—
- Alibaba CloudChina (Chengdu)cn-chengduChengdu, CN—
- Alibaba CloudChina (Fuzhou)cn-fuzhouFuzhou, CN—
- Alibaba CloudChina (Guangzhou)cn-guangzhouGuangzhou, CN—
- Alibaba CloudChina (Hangzhou)cn-hangzhouHangzhou, CN—
- Alibaba CloudChina (Heyuan)cn-heyuanHeyuan, CN—
- Alibaba CloudChina (Hong Kong)cn-hongkongHong Kong, HK—
- Alibaba CloudChina (Hohhot)cn-huhehaoteHohhot, CN—
- Alibaba CloudChina (Nanjing)cn-nanjingNanjing, CN—
- Alibaba CloudChina (Qingdao)cn-qingdaoQingdao, CN—
- Alibaba CloudChina (Shanghai)cn-shanghaiShanghai, CN—
- Alibaba CloudChina (Shenzhen)cn-shenzhenShenzhen, CN—
- Alibaba CloudChina (Ulanqab)cn-wulanchabuUlanqab, CN—
- Alibaba CloudChina (Zhangjiakou)cn-zhangjiakouZhangjiakou, CN—
- Alibaba CloudChina (Zhongwei)cn-zhongweiZhongwei, CN—
- Alibaba CloudGermany (Frankfurt)eu-central-1Frankfurt, DE—
- Alibaba CloudUK (London)eu-west-1London, UK—
- Alibaba CloudSaudi Arabia (Riyadh)me-central-1Riyadh, SA—
- Alibaba CloudUAE (Dubai)me-east-1Dubai, AE—
- Alibaba CloudMexico (Mexico City)na-south-1Mexico City, MX—
- Alibaba CloudUS East (Virginia)us-east-1Ashburn, US—
- Alibaba CloudUS West (Silicon Valley)us-west-1San Jose, US—
| # | Provider | Region | Location | Latency |
|---|---|---|---|---|
| Alibaba Cloud | Japan (Tokyo) ap-northeast-1 | Tokyo, JP | — | |
| Alibaba Cloud | South Korea (Seoul) ap-northeast-2 | Seoul, KR | — | |
| Alibaba Cloud | Singapore ap-southeast-1 | Singapore, SG | — | |
| Alibaba Cloud | Malaysia (Kuala Lumpur) ap-southeast-3 | Kuala Lumpur, MY | — | |
| Alibaba Cloud | Indonesia (Jakarta) ap-southeast-5 | Jakarta, ID | — | |
| Alibaba Cloud | Philippines (Manila) ap-southeast-6 | Manila, PH | — | |
| Alibaba Cloud | Thailand (Bangkok) ap-southeast-7 | Bangkok, TH | — | |
| Alibaba Cloud | China (Beijing) cn-beijing | Beijing, CN | — | |
| Alibaba Cloud | China (Chengdu) cn-chengdu | Chengdu, CN | — | |
| Alibaba Cloud | China (Fuzhou) cn-fuzhou | Fuzhou, CN | — | |
| Alibaba Cloud | China (Guangzhou) cn-guangzhou | Guangzhou, CN | — | |
| Alibaba Cloud | China (Hangzhou) cn-hangzhou | Hangzhou, CN | — | |
| Alibaba Cloud | China (Heyuan) cn-heyuan | Heyuan, CN | — | |
| Alibaba Cloud | China (Hong Kong) cn-hongkong | Hong Kong, HK | — | |
| Alibaba Cloud | China (Hohhot) cn-huhehaote | Hohhot, CN | — | |
| Alibaba Cloud | China (Nanjing) cn-nanjing | Nanjing, CN | — | |
| Alibaba Cloud | China (Qingdao) cn-qingdao | Qingdao, CN | — | |
| Alibaba Cloud | China (Shanghai) cn-shanghai | Shanghai, CN | — | |
| Alibaba Cloud | China (Shenzhen) cn-shenzhen | Shenzhen, CN | — | |
| Alibaba Cloud | China (Ulanqab) cn-wulanchabu | Ulanqab, CN | — | |
| Alibaba Cloud | China (Zhangjiakou) cn-zhangjiakou | Zhangjiakou, CN | — | |
| Alibaba Cloud | China (Zhongwei) cn-zhongwei | Zhongwei, CN | — | |
| Alibaba Cloud | Germany (Frankfurt) eu-central-1 | Frankfurt, DE | — | |
| Alibaba Cloud | UK (London) eu-west-1 | London, UK | — | |
| Alibaba Cloud | Saudi Arabia (Riyadh) me-central-1 | Riyadh, SA | — | |
| Alibaba Cloud | UAE (Dubai) me-east-1 | Dubai, AE | — | |
| Alibaba Cloud | Mexico (Mexico City) na-south-1 | Mexico City, MX | — | |
| Alibaba Cloud | US East (Virginia) us-east-1 | Ashburn, US | — | |
| Alibaba Cloud | US West (Silicon Valley) us-west-1 | San Jose, US | — |
Frequently asked questions
Everything below is the precise methodology behind the numbers on this page.
What is an Alibaba Cloud ping test?
An Alibaba Cloud (Aliyun) ping test measures the round-trip latency between your browser and a public-external Alibaba Cloud endpoint in each region. It uses HTTPS HEAD requests instead of ICMP, so it works from any browser without an Aliyun account. Lower numbers point to the Alibaba Cloud region that will give your users the lowest latency for ECS, OSS, ACK, and other Alibaba services.
How does this Alibaba Cloud ping test measure latency?
regionping pings the public-external OSS endpoint (https://oss-{region}.aliyuncs.com) for each Alibaba Cloud region — the same hostname any non-VPC client would use. Mainland-China regions transit through Alibaba's global accelerator network, so intercontinental latency typically reflects the public-internet path rather than Alibaba's intra-cloud backbone. Five HEAD samples per region, drop high+low, median of three, up to 16 regions in parallel.
How does regionping measure latency?
Your browser sends one warmup HEAD request per region to prime DNS, TCP, and TLS, then issues five timed HEAD requests. The highest and lowest samples are dropped and the median of the remaining three is shown. Up to 16 regions are measured in parallel.
Why are the numbers higher than what ICMP ping shows?
regionping runs inside a browser, which cannot send ICMP packets. Every sample is an HTTPS HEAD request, so the measured time includes TCP and TLS overhead. Expect regionping numbers to sit roughly 10–30 ms above ICMP ping from the same machine. The ordering between regions is still faithful, which is what matters when choosing one.
Which cloud providers and regions are supported?
AWS (32 regions), Google Cloud (41 regions), Azure (40 regions), Oracle Cloud (37 regions), DigitalOcean (10 regions), IBM Cloud (12 regions), Alibaba Cloud (29 regions), Linode (21 regions), OVHcloud (8 regions), Vultr (10 regions), Hetzner (3 regions), Huawei Cloud (26 regions), Exoscale (7 regions), Scaleway (4 regions), Gcore (3 regions), and Contabo (3 regions). 286 public regions in total.
What do the green, yellow, and red latency values mean?
Green (under 80 ms) is what you want for interactive workloads — API calls, real-time messaging, game servers. Yellow (80–149 ms) is acceptable for most web apps but noticeable in chatty request patterns. Red (150 ms and above) signals a region that is likely far from your network path; usable for batch and background jobs but a poor choice for anything user-interactive.
Why did a region return “failed”?
Most common causes, in roughly decreasing order of likelihood: a corporate firewall or enterprise proxy blocking the provider domain, an active VPN routing the request through a path that drops it, ISP-level blocks on cloud object-storage hostnames, the provider not yet deploying (or having deprecated) the public endpoint in that region, or a browser extension such as an ad blocker or privacy tool intercepting the request. Failures are surfaced explicitly instead of hidden so you can cross-check from a different network.