🌐geocables

BETA

Calculate submarine cable routes, estimate latency, verify with real measurements

↓ Learn how it works

Resolving locations & calculating...

Straight-Line
—
Cable Route
—
Est. Latency
—
fiber ≈ 200k km/s
Route Type
—

📋 Connection Details

Point A—
Point B—
Coordinates A—
Coordinates B—
Cable Multiplier—
Crosses Ocean—
Route Details—
Data Source—
Building route...
No calculations yet
—
Route km
—
Hops
—
Est. RTT
—
Type
⚠️ Cable distances are approximate estimates based on geographic analysis. Actual routes depend on existing cable infrastructure, submarine cables, and peering points.
500+
Submarine Cables
1 900+
Landing Points
50K+
City Pairs
< 1s
Route Calculation
Features
Network infrastructure made visible
Three layers of analysis — from theoretical cable distances to real-world packet measurements.
📊

Smart Cable Routing

Dijkstra-based routing through real submarine cables and landing points from TeleGeography data. Accurate distance multipliers for land and undersea segments.

🌊

Submarine Cable Map

Interactive map showing every cable your data touches — backbone nodes, landing stations, and submarine segments with real geographic coordinates.

🔬

RIPE Atlas Verification

Launch real network measurements from probes worldwide. Compare theoretical estimates with actual RTT and hop-by-hop packet journeys with ISP geolocation.

⚡

Latency Estimation

Speed-of-light physics combined with cable distance to estimate latency. See the real-world overhead — how much slower actual routing is vs fiber limits.

🔍

IP & Domain Resolution

Enter cities, IP addresses, or domain names — everything is resolved to coordinates with hosting location identification and optimal cable route.

🗺️

Packet Journey Analysis

Traceroute hops enriched with city, country, ISP. Phases auto-detected: local → ISP → CDN → backbone → submarine cable. Visual RTT timelines.

How It Works
From two points to a complete picture
Three-step analysis reveals the hidden infrastructure connecting any two locations.
1

Enter any two points

City names, IP addresses, or domains. The system resolves coordinates, identifies countries, and determines whether the route crosses oceans.

2

Smart Route calculates the path

A graph algorithm finds the optimal route through landing points and submarine cables with accurate distance multipliers for each segment type.

3

Verify with live measurements

One click launches RIPE Atlas probes for real ping and traceroute. See actual RTT, identify every router, and find where your packet enters submarine cables.

Use Cases
Built for engineers. Useful for everyone.
🏗️

Network Engineers

Validate routing assumptions, estimate latency budgets, troubleshoot unexpected paths.

🎮

Gaming & Low-Latency

Understand your ping. Compare the physical speed limit vs reality for any server.

🏢

CDN & Cloud Planning

Choose optimal PoP locations based on submarine cable topology and landing proximity.

📚

Education & Research

Teach how the physical internet works. Visualize the gap between light speed and real routing.

ℹ️ About GeoCables — Submarine Cable Distance Calculator

How Does Internet Data Travel Between Countries?

Over 95% of intercontinental data travels through submarine fiber optic cables — physical wires laid on the ocean floor connecting continents. GeoCables calculates the actual distance your data travels through this cable infrastructure, not just the straight-line distance between two points.

The tool uses real submarine cable data from TeleGeography (500+ cables, 1900+ landing points) combined with a Dijkstra-based routing algorithm to find the optimal path through landing stations and backbone nodes. For trans-oceanic routes, it identifies which submarine cables your data most likely traverses.

Theory vs Reality: Why Is Real Latency Higher?

Light travels through fiber optic cable at approximately 200,000 km/s — about two-thirds the speed of light in vacuum. GeoCables estimates minimum latency using this physical constant. Real-world RTT is typically 1.5–4x higher due to routing overhead, optical amplifier delays, protocol processing, peering between networks, and suboptimal path selection. The RIPE Atlas measurement feature lets you see this overhead directly.