IP & Network

Site Distance

Geographic distance between two IPs or websites.

Origin IP / Destination IP Compute the great-circle distance between two IPv4 or IPv6 addresses. Accuracy is city-level, not street-level.

Try: Google ↔ Cloudflare Google US ↔ Hetzner DE Google ↔ Tokyo

142.250.190.78 → 95.216.0.1

7,944 kilometers · 4,936 miles

Distance

7,943.6 km (4,935.9 mi)

Straight-line distance over the Earth's surface (great-circle, Haversine formula).

Origin

142.250.190.78

United States

37.7510, -97.8220

Destination

95.216.0.1

Finland · Helsinki

60.1719, 24.9347

View both points on OpenStreetMap

About this tool

Site Distance measures the physical great-circle distance between any two hosts on the internet. Enter two domains, two IPs, or one of each — the tool resolves each to its IP, geolocates each IP to its registered city, and computes the Haversine distance between the two coordinate pairs. The answer is shown in both kilometres and miles, with the cities and countries labelled on a small map preview.

For each host we also report the country, region, city, and the ASN of the operator. This makes it easy to spot the common surprise — a "local" site that turns out to be served from a different continent because it sits behind a global CDN. Distance is computed at full precision and rounded to the nearest kilometre on display.

When to use this tool

Latency vs distance comparison. A ping of 80ms to a "nearby" server suggests it is actually overseas; site-distance tells you whether the suspicion is right.
CDN sanity checks. Confirm your CDN's nearest POP really is in the city its name suggests.
Compliance and data residency. Quickly verify that two services are or are not hosted on the same continent.
Curiosity. See how far the typical request to a popular site actually travels from your part of the world.

About the numbers

Distance is geographic, not network distance. A 500-km straight line may translate to a 50-ms or a 250-ms round-trip depending on fibre routes, peering, and the speed of light in glass (≈ 200,000 km/s in fibre = 5 µs per kilometre, doubled for the return trip). For latency-sensitive comparisons, pair this with the Ping tool to measure the real round-trip; for geography only, distance is enough.

Frequently asked questions

How accurate is the distance?

As accurate as the IP geolocation behind it — typically city-level (10–50 km) for residential and corporate IPs, country-level (potentially hundreds of km off) for hosting and mobile carriers. The Haversine math itself is exact; uncertainty comes entirely from how precisely we can locate each endpoint. If both IPs are in big city centres, you can trust the number; if one is a cloud IP, treat it as approximate.

Why is the result not the actual network latency?

Because light in optical fibre travels at about 200,000 km/s (slower than in vacuum) and packets rarely take the straight-line path. A request from Berlin to Tokyo (9,000 km) has a theoretical minimum round-trip of 90 ms; real-world routes hit 200+ ms due to peering detours and queuing. For measured latency use the Ping tool — geography is the lower bound, not the answer.

Can I compare a CDN endpoint to my home IP?

Yes. Enter your own public IP in one field and a CDN-served hostname in the other; the tool geolocates both and gives you the distance. Note that the CDN may be served from a POP in your country (in which case the distance will be small) or from the origin server far away (large distance) — both are valid outcomes and tell you whether your local CDN edge is doing its job.

Does this work for IPv6?

Yes — and for mixed IPv4 / IPv6 pairs. Each endpoint is geolocated independently, so you can compare an IPv6-only hostname against a legacy IPv4 host without issue. The distance is computed from coordinates, regardless of address family.