Menu

I wanted to see which subsea cable my packets cross. The cloud couldn't trace, and the database put Helsinki in Phoenix
📰

I wanted to see which subsea cable my packets cross. The cloud couldn't trace, and the database put Helsinki in Phoenix

DEV Community: go·Affan Shaik·11 days ago
#E3gkY47p
#devtogo#devto#dev#trace#cable
Reading 0:00
15s threshold

The idea

When you open a website, your data passes through a dozen routers, a few ISPs, maybe a cable on the ocean floor, and several countries with their own data laws. None of that is visible. My pitch was:

Trace packets from your own computer, work out which networks, countries, and subsea cables they cross, check the route against data-sovereignty laws like GDPR, and draw it live on a 3D Earth.

The constraints: cost $0, use only open data, and say clearly what is measured and what is guessed.

Live demo: packetpulse-eta.vercel.app Code, data and tests: github.com/Flotrpy/PacketPulse

Scoping it down so it was buildable

Measurement: plain traceroute (ICMP/UDP with rising TTL), written from scratch in Go with raw sockets. Traceroute never sees a cable or a country; everything past the IP addresses and round-trip times is inference.

Data: only free sources.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.