League of Legends Ping Test
You vs friend
Advanced
About League of Legends ping
Test your League of Legends ping from the browser. LoL runs each region on a single platform shard — EUW in Amsterdam, EUNE in Frankfurt, NA, KR, BR and the rest — so the datacenter your account is tied to sets your latency floor. This tool probes a server near every LoL shard and ranks them by round-trip time.
LoL ping guide: excellent under 50 ms · good under 90 ms · playable under 120 ms · rough past 200 ms.
League of Legends server regions
| Region | Server location | Probe endpoint | Datacenters |
|---|---|---|---|
| 🇪🇺 EUW1 | Amsterdam, NL | eu-west-2 | 1 |
| 🇪🇺 EUN1 | Frankfurt, DE | eu-central-1 | 1 |
| 🇹🇷 TR1 | Istanbul, TR | il-central-1 | 1 |
| 🇷🇺 RU | Stockholm, SE | eu-north-1 | 1 |
| 🇺🇸 NA1 | Chicago, USA | us-east-2 | 1 |
| 🇧🇷 BR1 | São Paulo, BR | sa-east-1 | 1 |
| 🌎 LA1 | Miami / LATAM N | us-east-1 | 1 |
| 🌎 LA2 | Santiago / LATAM S | sa-east-1 | 1 |
| 🇰🇷 KR | Seoul, KR | ap-northeast-2 | 1 |
| 🇯🇵 JP1 | Tokyo, JP | ap-northeast-1 | 1 |
| 🇦🇺 OC1 | Sydney, AU | ap-southeast-2 | 1 |
| 🇵🇭 PH2 | Manila, PH | ap-east-1 | 1 |
| 🇸🇬 SG2 | Singapore | ap-southeast-1 | 1 |
| 🇹🇭 TH2 | Bangkok, TH | ap-southeast-7 | 1 |
| 🇹🇼 TW2 | Taipei, TW | ap-east-2 | 1 |
| 🇻🇳 VN2 | Ho Chi Minh, VN | ap-southeast-7 | 1 |
How this maps to in-game LoL ping
League of Legends runs each region on its own platform shard in a single datacenter. Browsers can't send the game's UDP, so this test fires HTTPS probes to the nearest cloud region beside each shard and ranks them by round-trip time. Your in-client ping reads a little lower, but the ordering of shards is reliable — it tells you which region is genuinely fastest for you.
LoL ping — frequently asked
What is a good ping for League of Legends?
Why does my shard matter for ping?
Is it worth transferring shards for lower ping?
Other ping tests
How this maps to in-game ping
Real game traffic is UDP; browsers can't open raw sockets. We probe AWS S3 regional endpoints (anycast-free HTTPS) and map each Valve SDR PoP to its nearest AWS region by great-circle distance. Expect ~5–15 ms TCP+TLS overhead vs in-game UDP, but the relative ordering of regions tracks closely.
Confidence: medium-high
Strong for relative ranking and choosing a region. Absolute numbers carry HTTPS overhead. Coverage is sparse in some places (mainland CN, parts of RU/ME) — those regions show — rather than a misleading number.