Gcore Ping Test
Find your closest, lowest-latency Gcore region. Gcore latency test from your browser. Measures the Object Storage path to every Gcore region.
3 Gcore regions measured · browser-based · no signup
3regions
- GcoreChicago (DRC2)s-drc2Chicago, US—
- GcoreLuxembourg (ED1)s-ed1Luxembourg, LU—
- GcoreSingapore (SGC1)s-sgc1Singapore, SG—
| # | Provider | Region | Location | Latency |
|---|---|---|---|---|
| Gcore | Chicago (DRC2) s-drc2 | Chicago, US | — | |
| Gcore | Luxembourg (ED1) s-ed1 | Luxembourg, LU | — | |
| Gcore | Singapore (SGC1) s-sgc1 | Singapore, SG | — |
Frequently asked questions
Everything below is the precise methodology behind the numbers on this page.
What is a Gcore ping test?
A Gcore ping test measures the round-trip latency between your browser and a Gcore public endpoint in each region. It uses HTTPS HEAD requests instead of ICMP so it works in any modern browser without a Gcore account. Lower numbers point to the Gcore region that will give your users the lowest latency for Cloud Compute, Object Storage, and Edge functions.
How does this Gcore ping test measure latency?
regionping pings Gcore Object Storage (https://{region}.cloud.gcore.lu) for each region. Gcore operates one of the largest independent CDN networks globally, and many of its cloud regions sit in the same datacenter as a Gcore POP — so latency is competitive with hyperscalers wherever they overlap. Five timed HEAD samples per region, 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.