Oracle Cloud Ping Test

Find your closest, lowest-latency Oracle Cloud region. Ping every Oracle Cloud Infrastructure region from your browser. 100% reliable across OCI Object Storage endpoints.

37 Oracle Cloud regions measured · browser-based · no signup

37regions
  • Oracle Cloud
    South Africa Central (Johannesburg)
    af-johannesburg-1Johannesburg, ZA
  • Oracle Cloud
    South Korea North (Chuncheon)
    ap-chuncheon-1Chuncheon, KR
  • Oracle Cloud
    India South (Hyderabad)
    ap-hyderabad-1Hyderabad, IN
  • Oracle Cloud
    Australia Southeast (Melbourne)
    ap-melbourne-1Melbourne, AU
  • Oracle Cloud
    India West (Mumbai)
    ap-mumbai-1Mumbai, IN
  • Oracle Cloud
    Japan Central (Osaka)
    ap-osaka-1Osaka, JP
  • Oracle Cloud
    South Korea Central (Seoul)
    ap-seoul-1Seoul, KR
  • Oracle Cloud
    Singapore (Singapore)
    ap-singapore-1Singapore, SG
  • Oracle Cloud
    Australia East (Sydney)
    ap-sydney-1Sydney, AU
  • Oracle Cloud
    Japan East (Tokyo)
    ap-tokyo-1Tokyo, JP
  • Oracle Cloud
    Canada Southeast (Montreal)
    ca-montreal-1Montreal, CA
  • Oracle Cloud
    Canada Southeast (Toronto)
    ca-toronto-1Toronto, CA
  • Oracle Cloud
    Netherlands Northwest (Amsterdam)
    eu-amsterdam-1Amsterdam, NL
  • Oracle Cloud
    Germany Central (Frankfurt)
    eu-frankfurt-1Frankfurt, DE
  • Oracle Cloud
    Spain Central (Madrid)
    eu-madrid-1Madrid, ES
  • Oracle Cloud
    France South (Marseille)
    eu-marseille-1Marseille, FR
  • Oracle Cloud
    Italy Northwest (Milan)
    eu-milan-1Milan, IT
  • Oracle Cloud
    France Central (Paris)
    eu-paris-1Paris, FR
  • Oracle Cloud
    Sweden Central (Stockholm)
    eu-stockholm-1Stockholm, SE
  • Oracle Cloud
    Switzerland North (Zurich)
    eu-zurich-1Zurich, CH
  • Oracle Cloud
    Israel Central (Jerusalem)
    il-jerusalem-1Jerusalem, IL
  • Oracle Cloud
    UAE Central (Abu Dhabi)
    me-abudhabi-1Abu Dhabi, AE
  • Oracle Cloud
    UAE East (Dubai)
    me-dubai-1Dubai, AE
  • Oracle Cloud
    Saudi Arabia West (Jeddah)
    me-jeddah-1Jeddah, SA
  • Oracle Cloud
    Saudi Arabia Central (Riyadh)
    me-riyadh-1Riyadh, SA
  • Oracle Cloud
    Mexico Northeast (Monterrey)
    mx-monterrey-1Monterrey, MX
  • Oracle Cloud
    Mexico Central (Querétaro)
    mx-queretaro-1Querétaro, MX
  • Oracle Cloud
    Colombia Central (Bogotá)
    sa-bogota-1Bogotá, CO
  • Oracle Cloud
    Chile (Santiago)
    sa-santiago-1Santiago, CL
  • Oracle Cloud
    Brazil East (São Paulo)
    sa-saopaulo-1São Paulo, BR
  • Oracle Cloud
    Brazil Southeast (Vinhedo)
    sa-vinhedo-1Vinhedo, BR
  • Oracle Cloud
    UK West (Newport)
    uk-cardiff-1Newport, UK
  • Oracle Cloud
    UK South (London)
    uk-london-1London, UK
  • Oracle Cloud
    US East (Ashburn)
    us-ashburn-1Ashburn, US
  • Oracle Cloud
    US Midwest (Chicago)
    us-chicago-1Chicago, US
  • Oracle Cloud
    US West (Phoenix)
    us-phoenix-1Phoenix, US
  • Oracle Cloud
    US West (San Jose)
    us-sanjose-1San Jose, US

Frequently asked questions

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

What is an Oracle Cloud ping test?
An Oracle Cloud ping test measures the round-trip latency between your browser and an Oracle Cloud Infrastructure (OCI) public endpoint in each region. It uses HTTPS HEAD requests instead of ICMP ping so it runs entirely in the browser, without an Oracle account. Lower numbers point to the OCI region that will give your users the lowest latency for Compute, OKE, Autonomous Database, and similar workloads.
How does this Oracle Cloud ping test measure latency?
regionping pings the OCI Object Storage regional endpoint (https://objectstorage.{region}.oraclecloud.com) for every commercial OCI region — a publicly resolvable host that consistently responds to anonymous HEAD requests. Five timed HEAD samples per region, the high and low are dropped, and the median of three is shown. Up to 16 regions are 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.