Counter-Strike 2 ping test
See your ping to the regions where Valve hosts official Counter-Strike 2 matches, from Virginia and Frankfurt to Hong Kong and Sydney, and which ones are closest to you. Your browser can't reach the game servers themselves, so each data centre is measured to the nearest public test server, which for most rows is in the same city or close to it. Official matchmaking picks the data centre for you, within the ping limit you set in the game, so the fastest rows here are where your matches will most likely run.
Is the game down? See the live CS2 status page. More ping tests: Valorant, League of Legends, World of Warcraft and Steam.
–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, SeattleSeattle, United States | North America | via AWS Oregon | – |
| 3 | US, CaliforniaLos Angeles, United States | North America | via AWS N. California | – |
| 4 | US, DallasDallas, United States | North America | via AWS Ohio | – |
| 5 | US, ChicagoChicago, United States | North America | via AWS Ohio | – |
| 6 | US, AtlantaAtlanta, United States | North America | via AWS N. Virginia | – |
| 7 | US, VirginiaSterling, United States | North America | via AWS N. Virginia | – |
| 8 | BrazilSão Paulo, Brazil | South America | via AWS São Paulo | – |
| 9 | ArgentinaBuenos Aires, Argentina | South America | via AWS São Paulo | – |
| 10 | ChileSantiago, Chile | South America | via AWS São Paulo | – |
| 11 | PeruLima, Peru | South America | via AWS São Paulo | – |
| 12 | United KingdomLondon, United Kingdom | Europe | via AWS London | – |
| 13 | EU, AmsterdamAmsterdam, Netherlands | Europe | via AWS London | – |
| 14 | EU, FrankfurtFrankfurt, Germany | Europe | via AWS Frankfurt | – |
| 15 | EU, FalkensteinFalkenstein, Germany | Europe | via AWS Frankfurt | – |
| 16 | EU, ViennaVienna, Austria | Europe | via AWS Frankfurt | – |
| 17 | EU, WarsawWarsaw, Poland | Europe | via AWS Frankfurt | – |
| 18 | EU, MadridMadrid, Spain | Europe | via AWS Aragón | – |
| 19 | EU, StockholmStockholm, Sweden | Europe | via AWS Stockholm | – |
| 20 | EU, HelsinkiHelsinki, Finland | Europe | via AWS Stockholm | – |
| 21 | United Arab EmiratesDubai, United Arab Emirates | Middle East | via AWS United Arab Emirates | – |
| 22 | South AfricaJohannesburg, South Africa | Africa | via AWS Cape Town | – |
| 23 | India, MumbaiMumbai, India | Asia | via AWS Mumbai | – |
| 24 | India, ChennaiChennai, India | Asia | via AWS Hyderabad | – |
| 25 | SingaporeSingapore | Asia | via AWS Singapore | – |
| 26 | Hong KongHong Kong | Asia | via AWS Hong Kong | – |
| 27 | JapanTokyo, Japan | Asia | via AWS Tokyo | – |
| 28 | South KoreaSeoul, South Korea | Asia | via AWS Seoul | – |
| 29 | AustraliaSydney, 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 CS2 servers: a browser cannot send anything to them. Each row is the public health-check address Amazon Web Services runs in the region nearest to that CS2 data centre (the data centre's own location is in the row), so the ping you see is the distance part of your in-game ping, and only a rough one where that region is far away. 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 28 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.