- 1 dedicated IP address
- 2 devices
- 5 open ports
- 1 TBmonthly bandwidth
- 50 Mbpsspeed
No commitment · Cancel anytime
Enter the IP your traffic goes to, or pick a test location. Our servers in Kansas City, San Jose, New York, Amsterdam & Singapore (US IPs) each ping it, we time your own connection where we can, and the table ranks them, so you can put your static IP from $4/mo where your traffic is fastest.
Updated
With a static IP over a tunnel, your traffic goes from your device to our server, and from our server to its destination. The test times both parts. Each of our server locations sends 5 pings to the address you choose and reports the average round-trip time, the jitter (how much the times vary) and any packet loss.
We also ping your own public IP from each location. Added together, the two parts are roughly what your traffic sees through that location, and the table is ranked by that total. If your router does not answer ping, we time a test server in your city instead: the city your IP is in, or the one you pick.
The nearest location is not always the fastest. Traffic follows the networks' own routes, not the map, and a route can detour through another continent. Routes to mainland China can differ by carrier, so the test has one target each for China Telecom, China Unicom and China Mobile.
For games, trading, remote desktop, voice calls and SSH, pick the location with the lowest total. Small differences of 5 to 10 ms rarely matter; packet loss and high jitter matter more than a few milliseconds, so the table ranks a location that lost more than one ping in five below the clean ones.
If your own connection could not be timed, pick where you are in the form and run the test again. Run the test again at the busy time of day for your destination, because evening congestion changes some routes.
GetAStatic gives you a dedicated public IPv4 over WireGuard on the location you pick. Five server locations: Kansas City (USA), San Jose (USA), New York (USA), Amsterdam (Netherlands) and Singapore. Every IP is a US IP address, whatever the server location, so the location you choose changes your route and your latency, not the country websites see.
The test needs an IPv4 address, not a domain name.
A destination that does not answer ping is not necessarily down: many servers and firewalls drop ping. Try another address on the same network, such as the website of the same company or the router in front of the server.
Plus for light use, Pro for most people, Ultra for full gigabit.
No commitment · Cancel anytime
No commitment · Cancel anytime
No commitment · Cancel anytime
Traffic follows the routes networks agree with each other, not the shortest line on a map. A route from a nearby city can detour through another country, while a farther one takes a direct cable. That is why the test pings from every location instead of guessing from distance.
Not to an arbitrary address: a speed test needs a server at the other end that sends or receives the data. Latency, jitter and packet loss are what decide how responsive a game, call or remote session feels, and those are what this test measures.
Many home routers, mobile networks and CGNAT setups drop ping from outside. When that happens we time a test server in your city instead: the city your IP is in, or the one you pick under 'Where are you?'. That is close to your own connection, not exact.
No. Five server locations: Kansas City (USA), San Jose (USA), New York (USA), Amsterdam (Netherlands) and Singapore. Every IP is a US IP address, whatever the server location. The location changes the route your traffic takes, and so its latency.
We ping it from each of our server locations and show you the results. We never store it. We keep the results (the times from each location) with the usual page-view details, which include your own IP. Normal web-server logs apply.
Have more questions? See the full FAQ →