Latency test: find the fastest location for your traffic

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

A public IPv4 address: your game server, API, office or customers' network.

We ping the address 5 times from each of our server locations, and ping your own IP the same way. If your IP does not answer, we ping a test server in your city instead. We never store the address you test.

The problem

What the latency test measures

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.

Why use GetAStatic?

What you get with a static IP in the fastest location

  • A dedicated public IPv4 on the server location your traffic reaches fastest
  • Your traffic always leaves from the same server location, so latency stays predictable
  • Open TCP or UDP ports in the dashboard: 5 open ports on Plus, unlimited open ports on Pro
  • VPN and IP in one price, from $4/mo, with a 30-day money-back guarantee
How it works

How to choose a location from the results

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.

Setup

How to test the route to your own server or service

The test needs an IPv4 address, not a domain name.

  1. Find the destination's IP. For a game server, use the address in your game client or server list. For a website or API, look up its address with nslookup or dig. Content delivery networks answer from a server near each of our locations, so a CDN address looks fast everywhere; test the origin server if you can.
  2. Turn off any VPN or relay, such as iCloud Private Relay, so we can time your own connection rather than the relay's.
  3. Run the test above and read the Total column. Run it once more at the time of day you use the connection most.
  4. Choose the fastest location when you order. Every IP is a US IP address, whatever the server location.

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.

Good to know

Limits of this test

  • It measures latency, jitter and packet loss, not speed. Speed (Mbps) to an arbitrary address needs a test server at the other end.
  • It uses ping. Some hosts and firewalls drop ping, so 'no reply' is common and does not mean the address is down.
  • Five pings per location give a snapshot, not an average over the day. Results for the same address are reused for one minute.
  • Privacy: we ping the address you enter and your own public IP, and show you the results. We never store the address you enter. We keep the results (the times from each location) with the usual page-view details, which include your IP. Normal web-server logs apply.
  • Each location gets one dedicated IPv4; Pro and Ultra include two. The device that uses it needs a WireGuard client (or a router that runs WireGuard). It is built for a stable address, not anonymity: the IP you connect from is logged.
Pricing

Choose your plan

Plus for light use, Pro for most people, Ultra for full gigabit.

Plus
$4/mo

 

  • 1 dedicated IP address
  • 2 devices
  • 5 open ports
  • 1 TBmonthly bandwidth
  • 50 Mbpsspeed

No commitment · Cancel anytime

Ultra
$10/mo

 

  • 2 dedicated IP addresses
  • 20 devices
  • Unlimited open ports
  • 5 TBmonthly bandwidth
  • 1 Gbpsspeed

No commitment · Cancel anytime

Unlimited
Need unlimited data?
  • 100 Mbpsspeed
  • Unlimitedbandwidth
  • 1 dedicated IP address
$15/mo
  • Inbound + outbound access
  • Instant activation
  • 30-day money-back guarantee
  • No annual commitment
  • Your price never goes up
FAQ

Questions, answered.

01Why is the closest location not always the fastest?

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.

02Can you test my speed in Mbps too?

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.

03Why does my own IP show no reply?

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.

04Does the server location change where websites think I am?

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.

05What do you do with the IP address I enter?

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 →