Huawei Cloud Ping Test
Find your closest, lowest-latency Huawei Cloud region. Huawei Cloud ping test for every OBS-served region from your browser.
26 Huawei Cloud regions measured · browser-based · no signup
26regions
- Huawei CloudAF-Cairoaf-north-1Cairo, EG—
- Huawei CloudAF-Johannesburgaf-south-1Johannesburg, ZA—
- Huawei CloudAP-Hong Kongap-southeast-1Hong Kong, HK—
- Huawei CloudAP-Bangkokap-southeast-2Bangkok, TH—
- Huawei CloudAP-Singaporeap-southeast-3Singapore, SG—
- Huawei CloudAP-Jakartaap-southeast-4Jakarta, ID—
- Huawei CloudAP-Manilaap-southeast-5Manila, PH—
- Huawei CloudCN East-Shanghai2cn-east-2Shanghai, CN—
- Huawei CloudCN East-Shanghai1cn-east-3Shanghai, CN—
- Huawei CloudCN East-Qingdaocn-east-4Qingdao, CN—
- Huawei CloudCN East-Qingdao2cn-east-5Qingdao, CN—
- Huawei CloudCN North-Beijing1cn-north-1Beijing, CN—
- Huawei CloudCN North-Beijing4cn-north-4Beijing, CN—
- Huawei CloudCN North-Ulanqab1cn-north-9Ulanqab, CN—
- Huawei CloudCN South-Guangzhoucn-south-1Guangzhou, CN—
- Huawei CloudCN South-Guangzhou2cn-south-2Guangzhou, CN—
- Huawei CloudCN Southwest-Guiyang1cn-southwest-2Guiyang, CN—
- Huawei CloudLA-Mexico Cityla-north-2Mexico City, MX—
- Huawei CloudLA-Santiagola-south-2Santiago, CL—
- Huawei CloudME-Riyadhme-east-1Riyadh, SA—
- Huawei CloudAP-Kuala Lumpurmy-kualalumpur-1Kuala Lumpur, MY—
- Huawei CloudNA-Mexico Cityna-mexico-1Mexico City, MX—
- Huawei CloudRU-Moscowru-northwest-2Moscow, RU—
- Huawei CloudLA-Buenos Airessa-argentina-1Buenos Aires, AR—
- Huawei CloudLA-São Paulosa-brazil-1São Paulo, BR—
- Huawei CloudTR-Istanbultr-west-1Istanbul, TR—
| # | Provider | Region | Location | Latency |
|---|---|---|---|---|
| Huawei Cloud | AF-Cairo af-north-1 | Cairo, EG | — | |
| Huawei Cloud | AF-Johannesburg af-south-1 | Johannesburg, ZA | — | |
| Huawei Cloud | AP-Hong Kong ap-southeast-1 | Hong Kong, HK | — | |
| Huawei Cloud | AP-Bangkok ap-southeast-2 | Bangkok, TH | — | |
| Huawei Cloud | AP-Singapore ap-southeast-3 | Singapore, SG | — | |
| Huawei Cloud | AP-Jakarta ap-southeast-4 | Jakarta, ID | — | |
| Huawei Cloud | AP-Manila ap-southeast-5 | Manila, PH | — | |
| Huawei Cloud | CN East-Shanghai2 cn-east-2 | Shanghai, CN | — | |
| Huawei Cloud | CN East-Shanghai1 cn-east-3 | Shanghai, CN | — | |
| Huawei Cloud | CN East-Qingdao cn-east-4 | Qingdao, CN | — | |
| Huawei Cloud | CN East-Qingdao2 cn-east-5 | Qingdao, CN | — | |
| Huawei Cloud | CN North-Beijing1 cn-north-1 | Beijing, CN | — | |
| Huawei Cloud | CN North-Beijing4 cn-north-4 | Beijing, CN | — | |
| Huawei Cloud | CN North-Ulanqab1 cn-north-9 | Ulanqab, CN | — | |
| Huawei Cloud | CN South-Guangzhou cn-south-1 | Guangzhou, CN | — | |
| Huawei Cloud | CN South-Guangzhou2 cn-south-2 | Guangzhou, CN | — | |
| Huawei Cloud | CN Southwest-Guiyang1 cn-southwest-2 | Guiyang, CN | — | |
| Huawei Cloud | LA-Mexico City la-north-2 | Mexico City, MX | — | |
| Huawei Cloud | LA-Santiago la-south-2 | Santiago, CL | — | |
| Huawei Cloud | ME-Riyadh me-east-1 | Riyadh, SA | — | |
| Huawei Cloud | AP-Kuala Lumpur my-kualalumpur-1 | Kuala Lumpur, MY | — | |
| Huawei Cloud | NA-Mexico City na-mexico-1 | Mexico City, MX | — | |
| Huawei Cloud | RU-Moscow ru-northwest-2 | Moscow, RU | — | |
| Huawei Cloud | LA-Buenos Aires sa-argentina-1 | Buenos Aires, AR | — | |
| Huawei Cloud | LA-São Paulo sa-brazil-1 | São Paulo, BR | — | |
| Huawei Cloud | TR-Istanbul tr-west-1 | Istanbul, TR | — |
Frequently asked questions
Everything below is the precise methodology behind the numbers on this page.
What is a Huawei Cloud ping test?
A Huawei Cloud ping test measures the round-trip latency between your browser and a Huawei Cloud public endpoint in each region. It runs in the browser via HTTPS HEAD requests, so no Huawei Cloud account or local tooling is required. Lower numbers point to the Huawei Cloud region that will give your users the lowest latency for ECS, OBS, CCE, and other Huawei services.
How does this Huawei Cloud ping test measure latency?
regionping pings Huawei Cloud OBS, the S3-compatible object storage (https://obs.{region}.myhuaweicloud.com), for each region. Huawei's footprint is strongest in mainland China and APAC; non-APAC users routinely transit through China-Hong Kong-Singapore peering, which dominates the measured RTT. Five HEAD samples, 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.