regionping

IBM Cloud Ping Test

Find your closest, lowest-latency IBM Cloud region. Browser-based ping test for IBM Cloud Object Storage regions and resiliency zones.

12 IBM Cloud regions measured · browser-based · no signup

12regions
  • IBM Cloud
    Australia (Sydney)
    au-sydSydney, AU
    —
  • IBM Cloud
    Brazil (São Paulo)
    br-saoSão Paulo, BR
    —
  • IBM Cloud
    Canada (Montreal)
    ca-monMontreal, CA
    —
  • IBM Cloud
    Canada (Toronto)
    ca-torToronto, CA
    —
  • IBM Cloud
    EU Germany (Frankfurt)
    eu-deFrankfurt, DE
    —
  • IBM Cloud
    EU Spain (Madrid)
    eu-esMadrid, ES
    —
  • IBM Cloud
    UK (London)
    eu-gbLondon, UK
    —
  • IBM Cloud
    India (Chennai)
    in-cheChennai, IN
    —
  • IBM Cloud
    Japan (Osaka)
    jp-osaOsaka, JP
    —
  • IBM Cloud
    Japan (Tokyo)
    jp-tokTokyo, JP
    —
  • IBM Cloud
    US East (Washington DC)
    us-eastWashington DC, US
    —
  • IBM Cloud
    US South (Dallas)
    us-southDallas, US
    —

Frequently asked questions

Everything below is the precise methodology behind the numbers on this page.

What is an IBM Cloud ping test?
An IBM Cloud ping test measures the round-trip latency between your browser and an IBM Cloud public endpoint in each region. It uses HTTPS HEAD requests rather than ICMP, so it works without a local CLI or IBM Cloud credentials. Lower numbers point to the IBM Cloud region that will give your users the lowest latency for IBM Cloud Object Storage, Code Engine, Kubernetes Service, and adjacent workloads.
How does this IBM Cloud ping test measure latency?
regionping hits IBM Cloud Object Storage S3-compatible endpoints (https://s3.{region}.cloud-object-storage.appdomain.cloud) for each region. The latency reflects the path through IBM's consolidated edge plus the regional COS ingress. Five timed HEAD samples per region, drop high and low, median of three. Up to 16 regions measured 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.