When the Internet Breaks

Final lesson — and it begins with the cry heard in every home on earth: "the Wi-Fi is broken!" Before this course, that sentence was a fog with a router in it. Now you know the truth: "the internet" isn't one thing that breaks. It's a chain of stops you can name — device, hallway, front door, provider, phone book, destination — and a failure is always somewhere in particular. Finding where is not wizardry. It's walking the chain you already know, one link at a time, and the walk is this course's parting gift.

Walk the chain

The order matters: near to far, cheap checks first.

1. Your device. Is it alone in its suffering? If another phone in the house is happily streaming, the network is fine and one guest has a problem — usually its lease or its radio. The fix you already understand: toggle Wi-Fi off and on (a fresh check-in at the front desk, new lease, clean orientation).

2. The hallway. All devices struggling, but only in the far bedroom? That's not the internet — that's Unit 1's three tariffs (distance, walls, the fridge) taxing the radio. Stand near the router and retest: better means coverage, not connectivity.

3. The front door. Everyone, everywhere in the house, nothing loads? Now suspect the router itself, and perform the sacred restart knowingly: it clears the doorman's thousand-conversation confusion and re-leases the building's own address from the provider. Give it two blinking minutes.

4. The road to town. Still dead after the restart? The likeliest truth is the honest fine print from the routers lesson: the mesh routes around damage, your driveway can't. The one road between your house and your provider — or the provider's own neighborhood equipment — is down. Their status page (on your phone's mobile data — a different road entirely, which is the whole diagnostic point) or a neighbor's identical grief confirms it. Nothing in your house can fix this one; you're allowed to make tea.

5. The phone book and the far end. Internet fine, but one site sick? Read the symptom like lesson 4 and lesson 2 taught you: "can't find the site" is a lookup problem; "can't reach it" is a dark house; a 404 is the wrong door in a lit house; a 5xx is the site's own kitchen on fire. None of these is your equipment — and remember the branch libraries: sometimes a famous front page stays up while its deeper rooms wobble.

That's the whole method: name the layer, test the layer, move outward. Guessing replaced by walking.

Built to break, built to heal

One closing thought to carry out the door. The internet breaks somewhere constantly — cables cut, buildings dark, routes flapping — and yet your evening mostly proceeds, because every layer you've met was designed by people who assumed breakage: numbered parcels that get re-asked, a mesh that routes around damage, leases that expire and heal, caches and branches that serve through outages, seals that assume eavesdroppers. Nothing about the internet is perfect; everything about it is prepared. There are worse philosophies to borrow.

And that's Network Foundations I — signals to packets, addresses to routes, roads to the city on top. When the hands-on labs land for this course, the first tool you'll meet is the one that lists the hops of Unit 2's relay before your eyes. Until then, two fine roads from here: Database Foundations I, where the city's buildings keep their facts — or Web Foundation I, where you stop touring the city and start building in it. The map is yours now. Enjoy knowing what the blinking lights mean.