Apex Legends ping test
See your ping to the Apex Legends data centres, from us-east-1 in Virginia to ap-southeast-2 in Sydney, and which one is closest to you. Apex runs its game servers on Amazon Web Services, and the game's list names most data centres by their Amazon region code, such as eu-central-1 for Frankfurt. Your browser can't reach the game servers themselves, so each data centre is measured to Amazon's public test address in the Amazon region with the same code. Amazon has no region called us-central-1, so that row is measured to Ohio and is only a rough guide. The data centre with the lowest ping here is the one to pick on the game's launch screen.
Is the game down? See the live Apex status page.
–ms
Median ping. Start the test to send 40 pings, one after another.
- Ping
- Spike
- Median
- Min
- –
- Average
- –
- Max
- –
- Jitter
- –
- Lost
- –
Each server gets a warm-up request and four timed pings; the table shows the fastest. Four servers are tested at a time.
–ms
Best ping. The table sorts itself as answers come in; servers that don't answer move to the end.
| # | Location | Region | Network | Ping |
|---|---|---|---|---|
| 1 | Nearest Cloudflare data centre | Nearest to you | Cloudflare | – |
| 2 | us-east-1Northern Virginia, United States | North America | via AWS N. Virginia | – |
| 3 | us-central-1United States | North America | via AWS Ohio | – |
| 4 | us-west-2Oregon, United States | North America | via AWS Oregon | – |
| 5 | sa-east-1São Paulo, Brazil | South America | via AWS São Paulo | – |
| 6 | eu-central-1Frankfurt, Germany | Europe | via AWS Frankfurt | – |
| 7 | ap-northeast-1Tokyo, Japan | Asia | via AWS Tokyo | – |
| 8 | ap-east-1Hong Kong | Asia | via AWS Hong Kong | – |
| 9 | ap-southeast-1Singapore | Asia | via AWS Singapore | – |
| 10 | ap-southeast-2Sydney, Australia | Oceania | via AWS Sydney | – |
Under 100 ms green · 100 to 250 ms amber · over 250 ms red
Your recent tests
Kept in this browser only; we don't store your results.
What is a good ping?
Ping is the time a small message takes to reach a server and come back, in milliseconds. The lower it is, the faster games, calls and websites react. These are the usual ranges:
Feels instant. Typical for fibre or cable to a nearby server.
Fine for online games, video calls and everything else.
Noticeable in fast games; calls still work.
Games lag and calls talk over each other.
Distance sets the floor: light in fibre needs about 1 ms for every 100 km there and back, so a server on another continent can't answer in 20 ms however good your line is.
How this test works
Your browser sends small HTTPS requests and times how long each answer takes. The first request opens the connection and isn't counted, so the timed pings measure the round trip rather than connection setup.
None of these are Apex servers: a browser cannot send anything to them. Each row is the public health-check address Amazon Web Services runs in the region whose code the game uses for that data centre (for us-central-1, which is not an Amazon region, the Ohio region), so the ping you see is the distance part of your in-game ping. The game adds a few milliseconds of its own.
The servers aren't ours. "Nearest Cloudflare data centre" is the Cloudflare location that delivers this site to you; it answers by itself, without contacting our server. The other 9 are the public health-check addresses Amazon Web Services runs in each of its regions, which answer instantly and stand in well-known places.
One-server tests send 40 pings one after another and report the median, which isn't thrown off by a single slow ping, plus the minimum, average and maximum, jitter and lost pings. The world test reports the fastest of four pings per server, the value closest to the network's real delay. Expect a few milliseconds more than the ping command shows.