How Internet Connections Actually Work

Getting the Internet Right: Part 2 of 12

Before we start talking about DSL versus cable versus fiber versus everything else, it helps to have a basic mental model for what's actually happening when your office connects to the internet. You don't need to understand this at an engineering level. But having even a rough picture of how data moves makes it much easier to understand why different connection types behave so differently, and why some problems that seem mysterious are actually pretty straightforward once you see the plumbing.

If you read the first post in this series, Your ISP Is the Foundation Everything Else Sits On, you already know that speed isn't the only thing that matters and that consistency is what makes or breaks voice and video. This post is about understanding why some connections are consistent and others aren't, by looking at what's physically happening between your office and the rest of the internet.

The physical part: getting data from here to there

At the most basic level, your internet connection is a physical thing. It's a wire, or a beam of light, or a radio signal, or a signal bounced off a satellite. Something has to physically carry your data from the equipment in your office to the equipment your internet provider operates, and from there to the broader internet.

The type of physical medium matters a lot. Copper wire behaves differently than fiber optic cable, which behaves differently than a wireless signal. Each one has different characteristics when it comes to how much data it can carry, how far it can carry it before the signal degrades, and how susceptible it is to interference from the environment.

Think of it like plumbing, because that analogy actually holds up surprisingly well. The pipe connecting your building to the water main could be a half inch copper pipe, a two inch PVC pipe, or a six inch main line. They all carry water. But the diameter of the pipe, the material it's made of, and the pressure behind it all determine how much water you can actually get at any given moment, and whether the flow is steady or whether it sputters when your neighbor turns on their sprinklers.

Internet connections work on a similar principle. The physical medium determines the theoretical maximum capacity. But what you actually experience depends on a bunch of factors beyond just the raw capacity of the wire or signal.

The last mile: where most of the action is

You'll sometimes hear the phrase "last mile" in conversations about internet service. This refers to the connection between your building and your ISP's nearest facility, which is usually called a central office, a headend, or a point of presence depending on the type of provider. Despite the name, it's not always a mile. It could be a few hundred feet or it could be several miles.

The last mile is where most of the interesting stuff happens, and it's where most connection types differ from each other. Once your data reaches your ISP's facility, it gets handed off to their backbone network, which is typically a large, fast fiber network that connects to the broader internet. That backbone is usually not the bottleneck. The last mile is.

This is why two businesses in the same city, paying similar prices, can have wildly different internet experiences. One office might be 500 feet from a fiber node. Another might be three miles from the nearest central office, connected by aging copper that was installed in the 1970s. The backbone they both connect to might be identical. But the last mile makes all the difference.

Shared versus dedicated: the fundamental split

If there's one concept from this entire series that you take away and remember, it should be this one: the difference between shared and dedicated connections.

A shared connection means that the capacity between your ISP's facility and your neighborhood (or building, or block) is split among multiple customers. Cable internet is the classic example. There's a certain amount of bandwidth available on the cable running down your street, and everyone connected to that cable is sharing it. When it's 2 AM and nobody else is using it, you might get blazing fast speeds. When it's 2 PM and every business on the block is running video calls and cloud backups simultaneously, you're all competing for the same capacity.

A dedicated connection means that the capacity between your ISP's facility and your building is yours alone. Nobody else touches it. If you're paying for 100 Mbps dedicated, you get 100 Mbps at 2 AM and you get 100 Mbps at 2 PM on the busiest day of the year. The consistency is dramatically different.

This distinction is the single biggest factor in whether a connection will reliably support voice and video. Remember from the last post: voice doesn't need much bandwidth, but it needs that bandwidth to be available consistently, with low latency, low jitter, and minimal packet loss. Shared connections can deliver that sometimes. Dedicated connections deliver that almost always. The price difference reflects this, and we'll get into specific numbers when we cover each connection type in later posts.

How data actually travels: packets and routing

You've probably heard the word "packets" before, especially if you've read the VoIP From the Ground Up series. Here's the simple version.

When you load a webpage, make a phone call, or send an email, the data doesn't travel as one continuous stream. It gets broken up into small chunks called packets. Each packet contains a piece of the data plus some addressing information that tells the network where it needs to go. These packets travel independently across the network, potentially taking different paths, and get reassembled at the destination.

For most internet activity, this system works beautifully. If a packet gets lost, the receiving end just asks for it again. If packets arrive out of order, they get sorted back into the right sequence. You never notice any of this because it happens in fractions of a second.

Voice traffic is the exception. As we covered in the VoIP series, voice calls happen in real time. When a packet carrying a piece of someone's sentence gets lost or delayed, there's no time to request it again. That piece of audio is simply gone. This is why voice is so much more sensitive to network conditions than regular web browsing or email. It's not that voice needs more from the network. It's that voice can't tolerate the kinds of hiccups that everything else handles invisibly. A VoIP quality test measures exactly this: whether your connection delivers packets consistently enough for real-time voice.

The equipment chain: more links than you think

Between your desk phone (or your computer running a softphone) and the person you're talking to, there are more pieces of equipment involved than most people realize. Understanding this chain helps explain why troubleshooting can be so frustrating, and why your ISP and your VoIP provider can both technically be telling the truth when they say the problem isn't on their end.

Starting from your desk and working outward, the chain looks something like this:

Your device connects to your local network switch or WiFi access point. That connects to your router. Your router connects to your modem, or in some setups the router and modem are the same box. The modem connects to whatever physical medium your ISP uses to reach their network, whether that's a copper pair, a coaxial cable, a fiber strand, or an antenna. From there, the signal hits your ISP's equipment at their nearest facility. From that facility, it travels across the ISP's backbone to an interconnection point where it gets handed off to the broader internet. Then it travels across potentially several more networks before reaching the destination.

A problem at any point in this chain can cause issues. A failing network switch in your office closet can cause packet loss that looks exactly like an ISP problem. A degraded copper pair between your building and the central office can cause jitter that looks exactly like a VoIP configuration problem. An overloaded interconnection point between your ISP and the VoIP provider's network can cause latency that neither one of them sees on their own internal monitoring.

This is the "blame game" problem that the voiptest.com homepage talks about. When something goes wrong, it's genuinely difficult to figure out which link in the chain is the weak one, because each provider can only see their own piece. Understanding that this chain exists, and roughly where the boundaries fall between what's yours, what's your ISP's, and what's your VoIP provider's, puts you in a much better position to have productive conversations when things go sideways.

Symmetrical versus asymmetrical: why upload matters

One more concept before we move on to specific connection types. Most residential internet connections, and many business connections, are asymmetrical. That means the download speed (data coming to you) is much faster than the upload speed (data going from you to the internet).

This makes sense for typical home internet usage. You're mostly consuming content: loading web pages, streaming video, downloading files. You rarely need to push large amounts of data in the other direction. A connection that gives you 300 Mbps down and 10 Mbps up works fine for that pattern.

Business use is different. Phone calls are a two way conversation, which means you're sending just as much voice data as you're receiving. Video conferencing is the same. Cloud backups are almost entirely upload. If your business has security cameras uploading footage, a point of sale system syncing transactions, employees working on shared documents in the cloud, or a server that external users need to connect to, the upload direction matters just as much as the download.

A lot of call quality problems come down to this asymmetry. The business has plenty of download speed, so speed tests look great. But the upload is congested during business hours because there simply isn't enough upload capacity for everything that needs it. And since most speed test tools emphasize download speed, the upload bottleneck often goes undiagnosed until someone specifically looks for it.

When we look at each connection type in the following posts, pay attention to whether the speeds are symmetrical or asymmetrical. It's one of the most practical differences between them, and it directly affects how many simultaneous voice and video calls your connection can reliably support.

Setting the stage

Now you have the basic framework. You know that the physical medium matters, that the last mile is where most variability happens, that shared and dedicated connections are fundamentally different things, that voice traffic is especially sensitive to inconsistency, and that upload speed is just as important as download for business use.

With that foundation in place, we're ready to start looking at specific connection types. We'll begin with the oldest one still in use.

Next up: DSL: The Connection That Outlived Its Welcome (Sometimes), what it is, where it still works, and where it's holding your business back.