The Internet Is a Series of Tubes
The most mocked metaphor in tech history was wrong about the details and accidentally right about the physics
Contents
<p>On 28 June 2006, a US senator named Ted Stevens stood up during a committee debate on net neutrality and delivered a sentence that would outlive most of his legislative career: “It’s not a big truck. It’s a series of tubes.” He went on to explain that the tubes could get “filled”, that an email he had been sent took days to arrive because the tubes were congested, and that we should therefore be cautious about letting anyone dump “enormous amounts of material” into them. The internet, predictably, did not respond with kindness.</p>
<p>The clip became a meme within days. Stevens, then chairing the very committee that regulated telecommunications, was held up as the perfect example of a lawmaker legislating something he plainly did not understand. And the mockery was fair — his grasp of the details was genuinely poor. But I have spent enough years pulling cables, tracing routes and swearing at fibre patch panels to tell you something slightly heretical: on the physics, the old man was closer to the truth than most of the people laughing at him.</p>
<h2 id="what-stevens-got-wrong">What Stevens got wrong</h2><div class="ad-unit ad-in-article" aria-label="Advertisement">
<span class="ad-label">Advertisement</span>
<ins class="adsbygoogle" style="display:block;text-align:center"
data-ad-client="ca-pub-3726833845844946"
data-ad-slot="3291553914"
data-ad-format="auto"
data-full-width-responsive="true"></ins>
<script>(adsbygoogle = window.adsbygoogle || []).push({});</script>
</div>
<p>Let’s be honest about the mistakes first, because there were several and they matter.</p>
<p>Stevens conflated bandwidth with latency. The idea that a large download somewhere else on the network would “fill the tube” and delay <em>your</em> email for days is not how packet-switched networks behave. His email did not take days because someone was streaming video; if a mail took days it was almost certainly a misconfigured server or a queue somewhere, not congestion on a shared pipe. Modern networks are packet-switched, not circuit-switched. Your data is chopped into small packets, each stamped with a destination, and those packets are interleaved with everyone else’s and reassembled at the far end. There is no single tube reserved for your message that a neighbour can plug up.</p>
<p>He also implied the internet was a simple, roughly linear thing — one big pipe with stuff flowing through it. It is nothing of the sort. It is a mesh: tens of thousands of independent networks, called autonomous systems, that agree to carry each other’s traffic under a protocol called BGP. When you load a page, your packets may cross five or six of these networks, each making its own selfish decision about the cheapest onward hop. There is no central tube and no one in charge of the whole thing.</p>
<p>So yes, as a description of <em>how routing works</em>, “a series of tubes” is wrong. That is the part worth mocking.</p>
<h2 id="what-stevens-got-accidentally-right">What Stevens got accidentally right</h2>
<p>Here is the uncomfortable bit for the people who made the T-shirts. Strip away the routing confusion and you are left with a claim about the physical layer — and the physical internet really is tubes.</p>
<p>The backbone of the global internet is fibre-optic cable: literally glass tubes carrying pulses of light. Between continents, that cable runs along the seabed. There are a few hundred submarine cables on the planet, each a bundle of fibres wrapped in steel and insulation, and something like 95% of all intercontinental data crosses them. Not satellites, not “the cloud” — physical cables lying in the dark on the ocean floor, occasionally severed by ship anchors or, memorably, by sharks that seem to enjoy biting them.</p>
<p>Those cables terminate at landing stations, feed into terrestrial fibre that runs through actual conduits under actual roads, and eventually reach the buildings — the data centres and exchange points — where networks physically meet and hand traffic to one another. When two networks “peer”, an engineer somewhere plugs a cable from one company’s router into another company’s router across a shared switch. It is astonishingly physical. The whole edifice of abstraction we call the internet rests, at the bottom, on someone having pulled a fibre through a duct.</p>
<p>Stevens said tubes. The backbone is glass tubes full of light. He was wrong about the traffic and right about the plumbing, which is a more interesting failure than the meme allows.</p>
<h2 id="a-quick-tour-down-the-stack">A quick tour down the stack</h2><div class="ad-unit ad-in-article" aria-label="Advertisement">
<span class="ad-label">Advertisement</span>
<ins class="adsbygoogle" style="display:block;text-align:center"
data-ad-client="ca-pub-3726833845844946"
data-ad-slot="3291553914"
data-ad-format="auto"
data-full-width-responsive="true"></ins>
<script>(adsbygoogle = window.adsbygoogle || []).push({});</script>
</div>
<p>You can watch the tubes yourself. Every operating system ships a tool that traces the path your packets take across those independent networks, hop by hop. On Linux or macOS:</p>
<div class="highlight"><div class="chroma">
<table class="lntable"><tr><td class="lntd">
<pre tabindex="0" class="chroma"><code><span class="lnt">1
</span></code></pre></td>
<td class="lntd">
<pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">traceroute vo.rs
</span></span></code></pre></td></tr></table>
</div>
</div><p>On Windows the equivalent is <code>tracert</code>. The output is a numbered list of routers your packets passed through, each with its round-trip time:</p>
<div class="highlight"><div class="chroma">
<table class="lntable"><tr><td class="lntd">
<pre tabindex="0" class="chroma"><code><span class="lnt">1
</span><span class="lnt">2
</span><span class="lnt">3
</span><span class="lnt">4
</span><span class="lnt">5
</span><span class="lnt">6
</span><span class="lnt">7
</span><span class="lnt">8
</span></code></pre></td>
<td class="lntd">
<pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">traceroute to vo.rs (203.0.113.10), 30 hops max, 60 byte packets
</span></span><span class="line"><span class="cl"> 1 _gateway (192.168.1.1) 0.512 ms
</span></span><span class="line"><span class="cl"> 2 10.0.0.1 8.104 ms
</span></span><span class="line"><span class="cl"> 3 core1.isp.example.net 12.44 ms
</span></span><span class="line"><span class="cl"> 4 ae-2.border.lon.example.net 15.90 ms
</span></span><span class="line"><span class="cl"> 5 ldn-ix.peering.example.net 16.71 ms
</span></span><span class="line"><span class="cl"> 6 edge.hoster.example.com 17.02 ms
</span></span><span class="line"><span class="cl"> 7 203.0.113.10 17.88 ms
</span></span></code></pre></td></tr></table>
</div>
</div><p>Each line is a real machine in a real building, and the jump in latency between hops three and four is often the moment your packets leave your ISP’s network and cross into someone else’s — a peering point, a physical handover. Run it to a server on another continent and you will see the round-trip time leap by 80 or 100 milliseconds at exactly the hop where the packets go underwater. That latency floor is not congestion; it is the speed of light in glass over thousands of kilometres of submarine cable. You are watching the tubes.</p>
<p>If you want to see the mesh rather than the line, look up the autonomous system numbers behind those hostnames. Tools like <code>whois</code> or public BGP looking-glasses will show you which company owns each network and who it peers with. The internet stops feeling like a cloud and starts feeling like a map of businesses shaking hands.</p>
<p>There is a subtlety here that matters for the tube metaphor. The path your packets take <em>out</em> to a server and the path the reply takes <em>back</em> are frequently not the same route. Each network makes its own selfish, moment-by-moment routing decision, so your request might cross London and Amsterdam while the response comes home via Paris. There is no reserved lane, no round-trip tube. That asymmetry is impossible to square with Stevens’s picture of a single pipe you fill up, and it is one of the reasons the metaphor breaks the instant you look at how routing actually behaves. The physical layer is tubes; the logical layer is a restless negotiation that reroutes around failures in seconds.</p>
<p>You can see that self-healing in action when something breaks. When a submarine cable is severed — and one is cut somewhere in the world every few days, usually by a fishing trawler or a ship’s anchor — traffic does not stop. BGP notices the path has vanished and the affected networks recompute routes around the damage, often before most users notice anything worse than a bit more latency. The system was built to survive exactly this. But “survive” is not the same as “unaffected”: a region served by only one or two cables can lose a large fraction of its capacity when a single one fails, which is why cable-cut events still make the news in places that lack redundancy. The tubes are real, physical, and vulnerable — and the cleverness is in the routing that pretends they aren’t.</p>
<h2 id="why-the-metaphor-keeps-mattering">Why the metaphor keeps mattering</h2>
<p>The reason I keep coming back to Stevens is not to defend a politician’s cluelessness. It is because the “series of tubes” mockery encouraged a whole generation to think of the internet as <em>immaterial</em> — as pure information, weightless, everywhere and nowhere. That framing is comforting and completely misleading, and it leads to bad intuitions.</p>
<p>If you think the internet is weightless, you do not think about where your data physically lives, who can physically reach it, or what happens when a single cable is cut and half a country loses connectivity — which happens more often than you would like. You do not think about the fact that “the cloud” is a warehouse with a landlord, a power bill and a jurisdiction. Understanding that the internet is physical is the first step to taking any of its politics seriously, from data sovereignty to the <a href="/story/cookies-on-the-internet/">small mechanisms of tracking and state that ride on top of it</a>. The tubes have owners, and the owners have interests.</p>
<p>It also matters for anyone who runs their own corner of it. The moment you stop renting from a hosting company and start caring about where your services physically sit, the abstraction dissolves fast — as anyone weighing <a href="/story/the-real-cost-of-self-hosting-electricity-time-and-what-you-actually-save/">the real, physical cost of self-hosting</a> discovers the first time they touch the electricity bill. There is no cloud. There is only someone else’s computer, plugged into a tube.</p>
<p>The physicality also explains why so much of internet governance is really about geography. When a country wants to censor or surveil, it does not reach into some abstract ether; it leans on the operators of the physical infrastructure inside its borders — the cables that land on its coast, the exchange points in its cities, the ISPs licensed to operate there. The reason a national firewall is even possible is that the tubes have to enter the country somewhere, through equipment somebody local owns and a regulator can compel. Understand the plumbing and the politics stops being mysterious: control of the network follows control of the hardware, which follows control of the land it sits on. The “series of tubes” gag made the internet sound like a folksy plumbing system when the truth is that plumbing is exactly the right frame for who holds power over it.</p>
<h2 id="the-verdict">The verdict</h2>
<p>Ted Stevens deserved the ribbing for the parts he got wrong: the traffic model, the idea of a shared pipe you can clog, the general air of a man reading a briefing note upside down. Packet switching and BGP are not tubes, and pretending they are will give you a wrong mental model of how the network routes and fails.</p>
<p>But the next time someone smugly repeats the meme, you get to be the annoying one at the table who points out that the backbone genuinely is glass tubes on the seabed, that “the cloud” is a building, and that the whole system is far more physical than the joke lets on. Stevens was a bad guide to how the internet <em>works</em> and an accidental prophet of what it is <em>made of</em>. That is a more useful thing to remember than the punchline.</p>
<p>The deeper lesson is that a good mental model has to hold both truths at once. The internet is logical and physical, abstract and concrete, a restless mesh of routing decisions running on top of glass and steel that someone had to lay. Get either half wrong and your intuitions fail: treat it as pure abstraction and you will be baffled by outages, jurisdiction and cost; treat it as a simple pipe and you will be baffled by routing, redundancy and the way a severed cable barely registers. The meme won because it was funny and half-true, which is the most durable kind of wrong.</p>
<p>Run a <code>traceroute</code> sometime and watch your packets crawl under an ocean. The tubes are real. They are just full of light, not water — and nobody, not even the senator, is filling them up on your behalf.</p>
Advertisement
Related Content
Advertisement
