Who invented the internet?

No single person did. ARPANET was built by teams of researchers in the late 1960s, TCP/IP was developed by Vint Cerf and Bob Kahn, and Tim Berners-Lee invented the World Wide Web in 1989–1991. It was a decades-long collaborative effort.

Is the internet the same as Wi-Fi?

No. Wi-Fi is just the wireless link between your device and your router. Your router then connects to your internet provider, which connects you to the wider internet. Wi-Fi can work without internet access (for example, to reach a local printer).

Why is my internet slow sometimes?

Common causes include network congestion during peak hours, a weak Wi-Fi signal or an overloaded router, the website's own servers being busy, and background apps using bandwidth. Speed tests measure your connection; if the site itself is slow, the problem may be at the other end.

Can the entire internet go down at once?

Effectively no. The internet was designed as a decentralized network of networks with no single point of failure, so a total global shutdown is essentially impossible by accident. Local and regional outages happen, and individual countries can restrict access within their borders.

How Does the Internet Work? — Explained Clearly

The internet is not a single machine or company — it is a global network of networks, owned and operated by thousands of organizations, all agreeing to exchange data using shared rules called protocols.

Every day, billions of people stream videos, send messages and shop online without thinking about what happens between tapping a screen and seeing a result. This guide traces that invisible journey: how your data is packaged and routed across the planet, the addressing systems that keep it all organized, the physical cables and data centres underneath it all, and who — if anyone — is actually in charge.

A very short history of the internet

1969: ARPANET, funded by the US Department of Defense's research agency, sends its first message between computers at UCLA and Stanford. It is a research network linking a handful of universities.
1983: ARPANET adopts TCP/IP as its standard communication protocol — the "flag day" when the modern internet's common language takes over.
1989–1991: Tim Berners-Lee, working at CERN in Switzerland, proposes and builds the World Wide Web: URLs to address pages, HTTP to fetch them, HTML to write them, and the first browser to view them.
1990s: commercial internet providers appear, easy browsers like Mosaic and Netscape arrive, and the web goes mainstream in the dot-com boom.
2000s to today: broadband replaces dial-up, Wi-Fi untethers devices, smartphones put the internet in every pocket, and streaming, social media and cloud computing reshape daily life.

Packets: how data travels

When you load a web page, your device breaks the request into small chunks called packets. Each packet carries the address of its destination and part of the message. Routers — specialized computers along the way — read each packet's address and forward it toward its destination, often by different routes. At the far end, the packets are reassembled in order. If a packet goes missing, it is simply re-sent.

Think of it like sending a book one page at a time through different couriers: each page is numbered and addressed, couriers choose whichever roads are clearest, and the recipient puts the pages back in order — requesting a re-send of any page that never arrives. This design is brilliantly resilient: there is no single road that everything must travel, so damage or congestion on one route simply sends packets another way. That resilience was one of the original design goals of ARPANET.

IP addresses and DNS

Every device on the internet has an IP address, a numerical label that identifies it (like a postal address). The original system, IPv4, uses 32-bit addresses — about 4.3 billion unique combinations. With billions of devices online, that pool has effectively run out, which is why the much larger IPv6 system (128-bit addresses) is gradually taking over.

Because numbers are hard for humans to remember, we use domain names such as example.com. The Domain Name System (DNS) acts as the internet's phone book, translating domain names into IP addresses so your browser knows where to send its packets. DNS is hierarchical: your request goes to a resolver (usually run by your internet provider), which consults root servers, then the servers for the top-level domain (like .com), then the domain's own authoritative servers. Results are cached at each level, which is why websites you visit often load a little faster.

What actually happens when you open a web page

Here is the step-by-step sequence behind a single click, usually completed in well under a second:

You type a URL or click a link. Your browser first checks its own cache — maybe it already has the page.
If not, the browser asks a DNS resolver to translate the domain name into an IP address.
The browser opens a connection to that IP address and — for secure sites — performs a TLS handshake, agreeing on encryption keys. This is the "S" in HTTPS.
The browser sends an HTTP request ("GET this page, please"), and the server responds with the page's HTML.
The browser parses the HTML and discovers it needs more files — images, stylesheets, scripts — so it fires off additional requests, many served from nearby CDN servers (more on those below).
The page renders on your screen.

The biggest factor in how fast this feels is latency — the round-trip time for signals to travel. Light in fibre-optic cable is fast, but crossing an ocean still takes tens of milliseconds each way, and every extra round trip adds up.

The internet vs. the World Wide Web

People often use the two terms interchangeably, but they are different things. The internet is the underlying infrastructure — the networks, cables and protocols. The World Wide Web is just one service running on top of it: the system of linked pages you browse.

Many things you do online are not "the web" at all. Email runs on its own protocols (SMTP, IMAP); video calls, online games and messaging apps each use theirs. An analogy: the internet is the road network, and the web is one particular delivery company driving on it. When the web was invented in 1989, the internet had already existed for two decades.

The role of protocols

Protocols are the shared languages of the internet. TCP/IP governs how packets are addressed and reliably delivered; HTTP/HTTPS governs how web browsers and servers exchange pages (the "S" means the connection is encrypted); and email, video calls and messaging apps each run on their own standard protocols. Because these standards are open, devices from different makers all interoperate.

Two transport protocols deserve a closer look. TCP guarantees that every packet arrives, in order — perfect for web pages, emails and file downloads, where a missing piece corrupts everything. UDP skips the guarantees for raw speed, which suits live video calls and online games, where a late packet is worse than a lost one. Modern web standards keep evolving too: HTTP/2 and HTTP/3 (built on a UDP-based protocol called QUIC) load pages faster by handling many requests more efficiently.

The physical internet: cables, data centres and CDNs

For something called the "cloud," the internet has a surprisingly heavy body. The vast majority of intercontinental data travels not by satellite but through undersea fibre-optic cables lying on ocean floors — satellites add too much latency for most traffic. On land, high-capacity backbone links connect cities and countries.

At the ends of those cables sit data centres: enormous buildings packed with servers that store and serve content. When people say their photos are "in the cloud," they mean on servers in buildings like these, run by companies such as Amazon, Google and Microsoft. To make popular content load fast, content delivery networks (CDNs) keep copies of videos, images and pages on servers close to you geographically — so the video you stream likely comes from a city nearby, not from across the world. Where networks meet to exchange traffic directly, they connect at internet exchange points, keeping data on the shortest possible path.

Who actually runs the internet?

No one — and that is by design. The internet is thousands of independent networks voluntarily interconnecting. A few organizations coordinate the shared resources: ICANN oversees domain names and IP address allocation, the IETF develops the open protocol standards through public discussion, and internet service providers (ISPs) carry traffic within their regions. Governments regulate internet use within their own borders. This decentralization is why the internet is so hard to shut down globally — though individual countries can and do restrict access within their territory.

From your home to the world

A typical journey looks like this: your device connects over Wi-Fi or mobile data to your internet provider, which forwards your packets across backbone networks — high-capacity fibre-optic links spanning continents and oceans — to the server hosting the content you asked for. The response travels back the same way, usually in well under a second.

Using the internet safely

Understanding the machinery helps you protect yourself on it. Look for HTTPS (the padlock icon) before entering sensitive information, keep devices and browsers updated so known vulnerabilities get patched, and use strong, unique passwords. For a deeper dive, read our guide on cybersecurity and protecting yourself online and our online shopping safety guide. And if you are curious how artificial intelligence now shapes what you see online — from recommendations to search results — that is a story in itself.

How Does the Internet Work?