regionping

OVHcloud Ping Test

Find your closest, lowest-latency OVHcloud region. OVHcloud regional ping test from your browser. Targets the high-performance S3 endpoints across OVH's global datacenter footprint.

8 OVHcloud regions measured · browser-based · no signup

8regions
  • OVHcloud
    Beauharnois (BHS)
    bhsBeauharnois, CA
    —
  • OVHcloud
    Frankfurt (DE)
    deFrankfurt, DE
    —
  • OVHcloud
    Gravelines (GRA)
    graGravelines, FR
    —
  • OVHcloud
    Roubaix (RBX)
    rbxRoubaix, FR
    —
  • OVHcloud
    Strasbourg (SBG)
    sbgStrasbourg, FR
    —
  • OVHcloud
    Singapore (SGP)
    sgpSingapore, SG
    —
  • OVHcloud
    London (UK)
    ukLondon, UK
    —
  • OVHcloud
    Warsaw (WAW)
    wawWarsaw, PL
    —

Frequently asked questions

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

What is an OVHcloud ping test?
An OVHcloud ping test measures the round-trip latency between your browser and an OVHcloud public endpoint in each region. It uses HTTPS HEAD requests rather than ICMP, so no OVH account or local tooling is needed. Lower numbers point to the OVHcloud region that will give your users the lowest latency for Public Cloud Instances, Object Storage, and Managed Kubernetes.
How does this OVHcloud ping test measure latency?
regionping uses the high-performance S3 endpoint (https://s3.{region}.perf.cloud.ovh.net) for each OVHcloud region. OVH's European backbone is one of the largest privately-owned networks in the EU, so intra-EU latency to OVH regions is often unusually low compared with US-based hyperscalers serving European users. Five HEAD samples per region, drop high+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.