See the connection.
Choose the location.

Compare VPS locations from your everyday connection. Choose a city with test IPs to check its route from your own computer. Test-only cities are labelled separately from deployment locations.

Test your connection. Choose your region.

Check your connection using regional test IPs, or run a browser latency test where available.

TEST IPs

Network information

Copy a test IP to check the route from your own computer.

TEST IPv4
130.94.107.41

An IPv6 test address is not available for this location.

How to test your connection

Open Command Prompt on Windows or Terminal on macOS / Linux and run the command for your system.

WINDOWSping -n 4 130.94.107.41macOS / LINUXping -c 4 130.94.107.41

Compare the round-trip times in the results. IPv6 testing requires a published IPv6 test address and an IPv6 connection.

Use your everyday connection.

Test on the connection your team or customers will actually use. A VPN or a different network can change the route and the result.

Review the range.

The median gives you a central result, while the minimum and maximum show how much the successful requests varied during this test.

Consider the whole workload.

Latency is one part of choosing a server. Compare memory, compute, storage, and the needs of your application alongside the network result.

Understanding the Looking Glass.

What does the Network Looking Glass measure?

Available tools depend on the selected location. Locations marked “Test IPs available” provide IPv4 addresses, plus IPv6 where published, for ping and traceroute from your own computer. Cities marked “Test location only” provide network targets without a listed VPS deployment option. Where a browser latency test is enabled, it measures a small HTTPS request to the selected location. HTTP latency is different from an ICMP ping measurement.

Why is a location marked as coming soon?

Its latency test is not available yet. Choose another available location or return when testing opens. No estimated results are shown for locations awaiting testing.

Why can my results change between tests?

Wi-Fi, mobile reception, a VPN, traffic on your connection, and network routing can affect results. Compare locations from the connection you expect to use and repeat the test when conditions change.

Are failed requests the same as packet loss?

No. A failed HTTP request can have several causes, including a timeout, a connection problem, or an unavailable regional test. The request counts shown by this tool are not an ICMP packet loss measurement.

Do I need an account or location permission?

No account or location permission is needed. Choose a test location and use its available tools. Browser latency results appear on this page and are not saved. Manual ping results appear in your own terminal.