IBM Cloud ping test
Latency from your browser to every IBM Cloud region (11), measured live, round after round. The fastest regions are greenest; click a column heading to sort.
Showing the last 20 rounds. The median, mean, min and max use every round.
| 1 | Americas Dallas | us-south |
– | – | – | – | – |
| 2 | Americas Sao Paulo | br-sao |
– | – | – | – | – |
| 3 | Americas Toronto | ca-tor |
– | – | – | – | – |
| 4 | Americas Montreal | ca-mon |
– | – | – | – | – |
| 5 | Americas Washington DC | us-east |
– | – | – | – | – |
| 6 | Europe Frankfurt | eu-de |
– | – | – | – | – |
| 7 | Europe London | eu-gb |
– | – | – | – | – |
| 8 | Europe Madrid | eu-es |
– | – | – | – | – |
| 9 | Asia Pacific Sydney | au-syd |
– | – | – | – | – |
| 10 | Asia Pacific Tokyo | jp-tok |
– | – | – | – | – |
| 11 | Asia Pacific Osaka | jp-osa |
– | – | – | – | – |
- How it's measured: your browser fetches a tiny file from each region in turn and times the reply. That is an HTTPS round trip, so it reads a little higher than a raw
ping, but it ranks regions the same way. - The first round only warms up connections: it's shown, but the median, mean, min and max leave it out. A region that doesn't answer within 3 seconds counts as failed for that round.
- Testing pauses while this tab is hidden, as browsers slow down background tabs and the times would be wrong.
Missing a provider or a region? Ask for it on GitHub.