regionping

Exoscale Ping Test

Find your closest, lowest-latency Exoscale region. Latency test for every Exoscale SOS zone. EU-only, fully browser-based.

7 Exoscale regions measured · browser-based · no signup

7regions
  • Exoscale
    Vienna (VIE-1)
    at-vie-1Vienna, AT
    —
  • Exoscale
    Vienna (VIE-2)
    at-vie-2Vienna, AT
    —
  • Exoscale
    Sofia (SOF-1)
    bg-sof-1Sofia, BG
    —
  • Exoscale
    Zurich (DK-2)
    ch-dk-2Zurich, CH
    —
  • Exoscale
    Geneva (GVA-2)
    ch-gva-2Geneva, CH
    —
  • Exoscale
    Frankfurt (FRA-1)
    de-fra-1Frankfurt, DE
    —
  • Exoscale
    Munich (MUC-1)
    de-muc-1Munich, DE
    —

Frequently asked questions

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

What is an Exoscale ping test?
An Exoscale ping test measures the round-trip latency between your browser and an Exoscale public endpoint in each zone. It uses HTTPS HEAD requests rather than ICMP, so it runs entirely in the browser without an Exoscale account. Lower numbers point to the Exoscale zone that will give your users the lowest latency for Compute Instances, SOS Object Storage, and Managed Kubernetes.
How does this Exoscale ping test measure latency?
regionping pings Exoscale Simple Object Storage (https://sos-{zone}.exo.io) across the European zones. Exoscale's independent European cloud has a flat regional topology — typically near-identical RTT between Geneva, Zurich, Frankfurt, and Munich from a typical EU origin. Five timed HEAD samples per zone, drop high+low, median of three, up to 16 zones 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.