regionping

IONOS Cloud Ping Test

Find your closest, lowest-latency IONOS Cloud region. IONOS Cloud latency test from your browser using regional Object Storage endpoints in Europe and the US.

4 IONOS Cloud regions measured · browser-based · no signup

4regions
  • IONOS Cloud
    Germany (Berlin)
    eu-central-3Berlin, DE
    —
  • IONOS Cloud
    Germany (Frankfurt)
    eu-central-4Frankfurt, DE
    —
  • IONOS Cloud
    Spain (Logroño)
    eu-south-2Logroño, ES
    —
  • IONOS Cloud
    US Central (Lenexa)
    us-central-1Lenexa, US
    —

Frequently asked questions

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

What is an IONOS Cloud ping test?
An IONOS Cloud ping test measures HTTPS round-trip latency from your browser to the public Object Storage endpoints listed on this page. regionping uses HEAD requests instead of ICMP ping to help you compare network paths for object storage API requests, without an IONOS Cloud account or local tools.
How does this IONOS Cloud ping test measure latency?
regionping sends one warmup HEAD request followed by five timed HTTPS HEAD requests to https://s3.{region}.ionoscloud.com. It drops the highest and lowest samples and shows the median of the remaining three. Up to 16 regions are measured in parallel, entirely in your browser.
Which IONOS Cloud locations does regionping measure?
This page measures IONOS Cloud Object Storage in Berlin, Frankfurt, Logroño, and Lenexa. When a location offers separate endpoints for user-owned and contract-owned buckets, regionping selects one endpoint so that location is counted once.
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 (33 regions), Google Cloud (43 regions), Azure (40 regions), Oracle Cloud (43 regions), DigitalOcean (13 regions), IBM Cloud (13 regions), Alibaba Cloud (30 regions), Akamai Cloud (23 regions), OVHcloud (13 regions), Vultr (14 regions), Hetzner (3 regions), Huawei Cloud (26 regions), Exoscale (8 regions), Scaleway (4 regions), Gcore (3 regions), Contabo (3 regions), Tencent Cloud (17 regions), IONOS Cloud (4 regions), and Backblaze B2 (4 regions). 337 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.