How did this page reach you?

You opened a browser, tapped a link, and this page appeared. It feels normal. But something fairly amazing just happened.

You might be reading this from Kerala. The computer that sent you this page could be in Mumbai, Singapore, Frankfurt or Virginia. So how did your phone find it, and how did the page cross that distance and land on your screen in under a second?

The internet is just a lot of connected computers

That’s genuinely it. There is no single giant machine called “the internet” — there are millions of computers and smaller networks, joined together, agreeing to pass messages along for each other.

When you open a website, your phone is asking another computer a question: can you send me this page? That computer sends it back, and your browser turns what arrives into the thing you’re looking at.

We usually draw the middle of that as a cloud, which is a comfortable way of avoiding the explanation. The internet is not a cloud. It is cables, mobile towers, Wi-Fi routers, networking machines the size of wardrobes, warehouse-sized data centres, and fibre-optic cable lying on the floor of the ocean. That last one is not a metaphor — most traffic between countries travels through cables on the seabed.

Getting out of your house

Say you type anshik.vercel.app into your phone. Before anything else can happen, your phone has to get onto the internet at all.

On Wi-Fi it hands the request to your router; on mobile data it reaches a nearby tower. Either way the wireless part is short — your phone is not beaming data to America, it’s reaching something a few hundred metres away. After that, almost the whole journey happens through cable.

Both paths lead to your internet provider — Jio, Airtel, BSNL, whoever — the entrance from your home into the wider internet. They don’t own the internet. They own one network inside it, connected to other networks, which connect to others, each passing your request a little closer to where it’s going.

But how does your phone know where to send it?

You know the site by name. Computers work with numbers — an IP address, which is the address of a machine on a network.

It’s the difference between a name and a delivery address. Your friend is “John”, but the courier needs House 25, Main Road, Kozhikode. Both point at the same person; only one gets a parcel there.

The system that translates one into the other is called DNS, and it works almost exactly like the contact list on your phone: you search for Mom, your phone finds the number, and you never think about the number again.

anshik.vercel.app
        ↓
       DNS
        ↓
   142.250.x.x   ← the actual address

Your message gets cut into pieces

Your phone now needs to say please send me the homepage. Rather than pushing that across the world as one lump, computers chop information into small pieces called packets — like posting a long book as numbered pages instead of one enormous parcel. If page 40 goes missing, the other end asks for page 40 again rather than the whole book.

Those pieces are steered by machines called routers. The name sounds technical; the job is a road sign. A packet arrives, the router reads where it’s headed and sends it down the right road, then the next router does the same, and so on until the pieces arrive and get put back in order.

No single router knows the full route. Each one only knows which direction is closer — and that’s the trick that lets a network of millions of machines work at all.

Sometimes your data goes under the ocean

This is the part I still find hard to be casual about. You’re in India, the server is in the United States, and somehow that distance has to be crossed:

Your phone
    ↓
Mobile tower / Wi-Fi router
    ↓
Your internet provider
    ↓
Fibre cable across India
    ↓
Cable landing station on the coast
    ↓
══════════════════════════════
   cable on the ocean floor
══════════════════════════════
    ↓
More cable, another country
    ↓
Data centre
    ↓
The website's computer

Inside those undersea cables are strands of glass thinner than a hair, and information moves through them as pulses of light. When you open a site hosted abroad, part of your request quite literally crosses an ocean as flashes of light. The wireless internet depends on an enormous amount of wire.

Fast, but not instant

Light in fibre travels around 200,000 km per second, which sounds like it should make distance irrelevant. But the cable route isn’t a straight line — India to a US server can be 13,000 km of actual cable — and there are routers along the way, the server’s own thinking time, and the entire return journey.

That usually adds up to 150–250 milliseconds. A second is 1,000, so call it a fifth of a second: your request crosses the planet, gets read, gets answered and comes back in less time than it takes to blink twice.

It’s also why distance still matters. Nothing anyone builds beats the speed of light, so the only real fix is to not go as far.

The computer at the other end, and the ones nearby

The machine running the website is called a server — a grand word for a computer whose job is to hand things to other computers. It works out what you asked for, usually looks it up in a database (just a place where an application keeps its information), and sends the answer back along the same route in reverse. Your browser turns what arrives into text, images, buttons and layout. That’s the page.

Except the fast sites cheat, sensibly. A company’s main server might be in Virginia, but it keeps copies of its images and files on machines in Mumbai, Singapore, London and a hundred other cities, so your phone talks to the copy nearby instead of the original far away. That’s a CDN — the name matters less than the idea: keep copies close to the people who need them. Your browser does a smaller version of the same thing, holding on to a logo it has already downloaded instead of asking twice. A lot of what feels like speed is really just avoided distance.

So what happened when you opened this page?

You tap a link
     ↓
Your phone asks DNS: where is this site?
     ↓
Wi-Fi router or mobile tower
     ↓
Your internet provider
     ↓
Other networks, router after router
     ↓
Thousands of kilometres of cable, possibly under an ocean
     ↓
The website's computer reads the request
     ↓
It sends the page back the same way
     ↓
Your browser turns it into what you're reading now

All of that in a fraction of a second, while you sat there waiting for it to hurry up.

The internet is more physical than it sounds

Cloud, online, server — the vocabulary makes it feel like somewhere else, a place made of nothing. It isn’t. A photo “in the cloud” sits on a real disk in a real building with a real electricity bill. Between you and it is real cable, some of it in the dark at the bottom of the sea, and real people keeping all of it running.

It isn’t magic. It’s a very large number of computers, cables and networks agreeing to pass messages to each other, very quickly. Which I think is better than magic, because it means somebody built it.