How the Internet Actually Travels

💻 Computers & the Internet · Lesson 36 of 50 · about 7 minutes

Advertisement

← Akademi · 💻 Computers & the Internet · Lesson 36 of 50 · about 7 min

Nothing on the internet is a wire from you to a website. Your message is chopped into packets — numbered chunks with a destination address — and each one is handed to the next router that is closer to the goal, free to take any path, reordered and reassembled at the far end. No central switchboard exists; the network is a mesh of millions of routers each consulting a table for “which neighbour is closest to that address”. This is why it survives damage: remove a link and traffic simply finds another way. A request and reply can cross the world in well under a second — light in fibre, plus the shuffle.

Addresses come twice: numeric IP addresses (v4 still running out, IPv6 replacing) are what packets carry, but humans type names, so DNS — a global, cached, hierarchical phone book — turns tukuk.org into numbers before anything moves. The lookup itself is a chain of referrals starting from root servers, and it is why “the site is down but my friend in the next town can open it”: their cached address differed from yours while records updated.

The physical truth surprises everyone: roughly 99% of intercontinental data — every video call, bank transfer and cat video crossing an ocean — rides fibre-optic cables on the seabed, a few dozen thick as a garden hose laid by specialised ships, repeater-powered every 60–100 km. Satellites carry a thin, slower slice. The cloud is not in the sky; it is warehouse rows in specific countries, and the internet is the sum of private networks that agreed to hand each other traffic at exchange points.

Key takeaways

  • Messages are packeted, routed independently and reassembled — no central switch exists
  • DNS is a cached global phone book; most “it works for me” mysteries are stale cache
  • Seabed fibre carries ~99% of intercontinental data — the cloud is physical

Check yourself

Why does the internet keep working after a major link is cut?

Go deeper

Advertisement
Advertisement