Backblaze B2 Ping Test
Find your closest, lowest-latency Backblaze B2 region. Backblaze B2 latency test for its US, European, and Canadian data regions. Browser-based, no account required.
4 Backblaze B2 regions measured · browser-based · no signup
4regions
- Backblaze B2Canada Eastca-east-006Toronto, CA—
- Backblaze B2EU Centraleu-central-003Amsterdam, NL—
- Backblaze B2US Eastus-east-005Reston, US—
- Backblaze B2US Westus-west-000Western US, US—
| # | Provider | Region | Location | Latency |
|---|---|---|---|---|
| Backblaze B2 | Canada East ca-east-006 | Toronto, CA | — | |
| Backblaze B2 | EU Central eu-central-003 | Amsterdam, NL | — | |
| Backblaze B2 | US East us-east-005 | Reston, US | — | |
| Backblaze B2 | US West us-west-000 | Western US, US | — |
Frequently asked questions
Everything below is the precise methodology behind the numbers on this page.
What is a Backblaze B2 ping test?
A Backblaze B2 ping test measures HTTPS round-trip latency from your browser to the B2 S3-compatible endpoints listed on this page. regionping uses HEAD requests instead of ICMP ping to help you compare network paths for object storage API requests. No Backblaze B2 account, bucket, or application key is required.
How does this Backblaze B2 ping test measure latency?
Your browser sends one warmup HEAD request to https://s3.{region}.backblazeb2.com, then collects five timed samples. regionping drops the highest and lowest and shows the median of the remaining three. Up to 16 regions are measured in parallel.
Which Backblaze B2 regions does regionping measure?
regionping measures US West, US East, EU Central, and Canada East using one S3-compatible endpoint per data region. Numeric endpoint suffixes identify storage clusters; they are not counted as additional geographic regions. US West is shown as a regional location because Backblaze documents data storage across Sacramento and Phoenix.
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.