Routers & Hops

A letter mailed from a village in Ethiopia to an apartment in Tokyo is handled by many hands: village post office, regional sorting center, international dispatch, a Japanese import hub, Tokyo's sorting floor, a neighborhood office, one bicycle. No single worker knows the whole journey. Each does one thing perfectly: read the address, pass it closer. Now you understand the middle of the internet, because it is exactly this — at the speed of light.

Routing: pass it closer

Your home router, it turns out, is the smallest member of an enormous guild. Between your house and any server stand chains of routers — industrial versions of your hallway box, installed by internet providers and backbone companies, wired to each other across cities, countries, and ocean floors. Each one plays the sorting-office game:

1. A packet arrives.
2. Read the destination address on the label.
3. Consult the guild knowledge: of my neighbors, which is closer to that part of the address space? (This is Unit 2 lesson 1's promise kept — addresses narrow like mailing addresses precisely so a router can steer by the broad part without knowing the destination personally.)
4. Hand it to that neighbor. Done. Next packet.

No router knows the full path. None needs to. Each knows its neighbors and which direction is closer — the guild equivalent of "Asia goes on that truck" — and the sum of many small correct decisions is a parcel crossing the planet.

Hops

Each handoff is called a hop, and a typical journey runs ten to twenty of them: your router, your provider's neighborhood equipment, up through its regional centers, across a backbone or under an ocean, down into the destination's provider, to the server's own doorstep. Every hop adds a sliver of time — which is where Unit 1's latency mostly lives. The road's length, remember, is the one thing more lanes never fix; now you can see the road itself: distance plus a dozen sorting stops.

Two properties of this relay quietly run the world:

• There is no single path. The guild is a mesh, not a chain — many routes exist between any two points. Two packets of one photo may travel different roads and arrive out of order... which Unit 1's reassembly already taught you the cure for. The pieces of this course are shaking hands.
• The mesh routes around damage. When a link dies — a cable cut by an anchor, a sorting office gone dark — neighboring routers notice and steer traffic along other roads, usually before you notice a thing. This resilience is not an accident; the network's ancestors were designed in the 1960s and 70s by people who wanted a system with no headquarters to fail, no single cut that stops the mail. You benefit from that paranoia every day.

The honest fine print: "routes around damage" describes the mesh's middle, not your driveway. Your home has one road to the guild — your provider — and when that fails, no cleverness upstream helps. The mesh is resilient; your last kilometer is not. (Unit 3's final lesson turns that into a diagnosis method.)

And with that, every piece of the map is on the table: addresses, desks, translation, names, doors, and the relay between. The unit's finale assembles all of it into one continuous story — a single packet's complete journey, every stop named. It's the best review this course knows how to give.