Home / Tools

Measure your latency to our Frankfurt servers

Real numbers from your own browser: round-trip time through the network to the origin, plus your connection details. Nothing is stored, nothing to install.

Your connection right now

Your IP
…
Edge location
…
Country
…
TLS
…

Read once, in your browser, from the network itself — no cookies, no tracking, nothing saved on our side.

Round-trip latency test

We send 12 tiny requests to the origin server in Frankfurt — each one unique, so it cannot be answered from a cache — and measure the round trip. This is exactly the path and speed your dynamic content takes.

0 / 12

Press the button — results in a couple of seconds.

How to read the numbers

Median RTT — the middle of the 12 measurements, the honest “typical” value. Best time — your fastest request, close to the physical limit of the path. Jitter — the difference between fastest and slowest: a large gap means an unstable connection (Wi-Fi, mobile network, congested ISP). Under 35 ms feels instant; around 100 ms is normal intercontinental traffic; above 200 ms is the other side of the planet.

Quick answers

Why do my numbers differ from speedtest results?

Speedtest measures bandwidth to a nearby server. This test measures latency to our specific routing path, including the network exchange in Frankfurt — which is what your website visitors actually experience.

Is my IP address stored anywhere?

No. The page reads it in your browser and shows it to you; nothing is sent to our databases or logs beyond the ordinary request that loaded this page.

The test says “far away” — should I still order?

It depends on the workload. Bots, backups and cron jobs do not care about latency at all. Interactive websites and remote desktops do — for those, our Frankfurt location is the closest we offer.

Happy with the numbers? Deploy a server in this network.

Related