Gcore ping test
Latency from your browser to every Gcore region (23), 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 | Netherlands Amsterdam | am3 |
– | – | – | – | – |
| 2 | Argentina Buenos Aires | syt |
– | – | – | – | – |
| 3 | Egypt Cairo | teg |
– | – | – | – | – |
| 4 | Hong Kong Hong Kong | hk2 |
– | – | – | – | – |
| 5 | Türkiye Istanbul | tii |
– | – | – | – | – |
| 6 | South Africa Johannesburg | jp1 |
– | – | – | – | – |
| 7 | Nigeria Lagos | lgs |
– | – | – | – | – |
| 8 | United Kingdom London | thn2 |
– | – | – | – | – |
| 9 | United States Los Angeles | la2 |
– | – | – | – | – |
| 10 | India Mumbai | ww |
– | – | – | – | – |
| 11 | United States New York | ny2 |
– | – | – | – | – |
| 12 | France Paris | pa5 |
– | – | – | – | – |
| 13 | Mexico Santiago de Querétaro | sqr |
– | – | – | – | – |
| 14 | United States Seattle | wbs |
– | – | – | – | – |
| 15 | South Korea Seoul | kx |
– | – | – | – | – |
| 16 | Singapore Singapore | sg1 |
– | – | – | – | – |
| 17 | Australia Sydney | sy4 |
– | – | – | – | – |
| 18 | Brazil São Paulo | sp3 |
– | – | – | – | – |
| 19 | Israel Tel Aviv | bzi |
– | – | – | – | – |
| 20 | Japan Tokyo | cc1 |
– | – | – | – | – |
| 21 | Germany Frankfurt | fr5 |
– | – | – | – | – |
| 22 | Kazakhstan Almaty | kal |
– | – | – | – | – |
| 23 | Azerbaijan Baku | dta |
– | – | – | – | – |
- 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.