regionping

DigitalOcean Ping Test

Find your closest, lowest-latency DigitalOcean region. Latency test for DigitalOcean Spaces regions. Lightweight, browser-only, no DO account.

10 DigitalOcean regions measured · browser-based · no signup

10regions
  • DigitalOcean
    Amsterdam 3
    ams3Amsterdam, NL
    —
  • DigitalOcean
    Bangalore 1
    blr1Bangalore, IN
    —
  • DigitalOcean
    Frankfurt 1
    fra1Frankfurt, DE
    —
  • DigitalOcean
    London 1
    lon1London, UK
    —
  • DigitalOcean
    New York 3
    nyc3New York, US
    —
  • DigitalOcean
    San Francisco 2
    sfo2Santa Clara, US
    —
  • DigitalOcean
    San Francisco 3
    sfo3Santa Clara, US
    —
  • DigitalOcean
    Singapore 1
    sgp1Singapore, SG
    —
  • DigitalOcean
    Sydney 1
    syd1Sydney, AU
    —
  • DigitalOcean
    Toronto 1
    tor1Toronto, CA
    —

Frequently asked questions

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

What is a DigitalOcean ping test?
A DigitalOcean ping test measures the round-trip latency between your browser and a DigitalOcean public endpoint in each region. It runs entirely in the browser using HTTPS HEAD requests, so no DigitalOcean account or local tooling is needed. Lower numbers point to the DigitalOcean datacenter that will give your Droplets, App Platform deployments, and managed databases the lowest user-perceived latency.
How does this DigitalOcean ping test measure latency?
regionping pings DigitalOcean Spaces (https://{code}.digitaloceanspaces.com) — the only DigitalOcean service with publicly resolvable per-region hostnames. Coverage is limited to the regions that have Spaces (e.g. NYC3, AMS3, FRA1, SGP1, BLR1, SYD1) but each one is reliable for round-trip timing. Five HEAD samples, 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.