The Internet Was Built to Route Around Obstacles — Web Proxies Are Proof
You paste a link into a proxy, hit enter, and the blocked page just… loads. Nobody thinks twice about it, honestly; why would you? But…
The Internet Was Built to Route Around Obstacles — Web Proxies Are Proof
You paste a link into a proxy, hit enter, and the blocked page just… loads. Nobody thinks twice about it, honestly; why would you? But there’s something wild happening underneath that, baked into the internet’s design since before anyone alive today was worried about school Wi-Fi blocking YouTube.

Web Proxies
The Network Was Never Built Around One Path
So back in the 60s, this RAND researcher, Paul Baran — he’s working on a problem that has literally nothing to do with browsing the web. The webdidn’t exist yet. He’s thinking about how communication networks survive damage. Not metaphorical damage. Real damage. Cold War era stuff, the kind where parts of a network might just… stop existing one day.
His fix was packet switching. Break data into small chunks, each one able to take a different path, rerouting on the fly if something’s blocking the way. No single point everything depends on. Cut one path, the rest still work.
That idea became the backbone of what eventually turned into the actual internet. Vint Cerf and Bob Kahn built on it with TCP/IP, and the core idea stuck around: data doesn’t care which route it takes. Just needs to get there. One path’s blocked? Fine, find another.
“The Internet Interprets Censorship as Damage”
There’s this line from John Gilmore — early internet guy, cypherpunk crowd — where he said the internet treats censorship like damage and just routes around it. Kind of become an unofficial motto in certain tech circles at this point. And honestly? Pretty accurate description of what’s literally happening, not just a clever quote.
Here’s the funny part though. None of this was designed with censorship in mind. Not even close. It was built for physical stuff — cables getting cut, hardware dying, nodes dropping offline. But that underlying idea, multiple paths, no single failure point, rerouting whenever something’s in the way — turns out it applies just as well to a totally different kind of obstacle. A blocked site is, weirdly, just another flavour of “damage” the network was already built to route around. Nobody planned that specific use. It just kind of fell out of the design almost by accident.
Where a Basic Proxy Fits Into This
A web proxy’s this tiny, almost silly little expression of that same idea, scaled way down. You’re not rerouting packets across some damaged physical network — you’re just picking a different path for one single request. Instead of your device talking straight to a blocked site, it talks to a proxy, and the proxy talks to the site for you. Same core idea, just happening at a way smaller, way more mundane scale. Path’s not available, find another one.
Kind of funny when you think about it — this dead-simple tool is quietly running on the same foundational logic as 1960s Cold War research about surviving network damage. Nobody spinning up a quick proxy to read one article is thinking about Paul Baran, obviously. But the DNA’s in there somewhere, buried a few layers down.
Worth Being Honest About the Limits Here
Not trying to make some “the internet wants to be free, anything goes” argument here. That same resilience letting someone read one blocked article also gets used for stuff that isn’t okay, and the tech itself doesn’t draw that line — people do. A proxy’s neutral. What it gets used for is a whole separate question, way more complicated than “well, the network was built this way, so.”
What’s actually interesting is just how deep this design principle goes, popping up in places you wouldn’t expect. Something like unblock-web.com — paste a link, page loads, no account, nothing to install — is a small, kind of unglamorous example of it. But structurally? Still doing exactly what the internet’s been built to do since day one. Find another way through when the direct path’s not there.
The Bigger Point
Most of the internet’s foundational design choices stay invisible to whoever’s actually using it day to day, which, honestly, is the whole point of good infrastructure — you’re not supposed to notice it working. But every so often, some tiny thing — like a blocked page suddenly loading because it went a different way — kind of accidentally echoes decisions made fifty-something years ago. People solving a totally different problem back then, and somehow it’s still quietly shaping a random Tuesday of browsing today.
Not bad for an idea that started with worrying about whether network cables would survive a crisis.
메타데이터
- post_id
- c2c32ce17bee
- slug
- the-internet-was-built-to-route-around-obstacles-web-proxies-are-proof-c2c32ce17bee
- url
- https://medium.com/@pulkitnagar2106/the-internet-was-built-to-route-around-obstacles-web-proxies-are-proof-c2c32ce17bee
- canonical_url
- https://medium.com/@pulkitnagar2106/the-internet-was-built-to-route-around-obstacles-web-proxies-are-proof-c2c32ce17bee
- author_url
- https://medium.com/@pulkitnagar2106
- status
- ok
- fetched_at
- 2026-08-07 06:10:39