What Is a CDN? How Content Delivery Networks Power Streaming

When you press play, the video rarely comes from a single faraway server. It comes from a content delivery network (CDN): a network of servers spread across cities and internet providers, holding copies of video close to viewers. CDNs are why streams can start in a second and why millions of people can watch the same final at once. This guide explains how CDN streaming works and what it means for you.

The problem CDNs solve

If every viewer fetched video from one central server:

• distance would add delay,
• the server and its connection would become a bottleneck,
• popular live events would overload it.

A CDN spreads the load across many servers near viewers.

How a CDN works

1. The streaming service keeps the master copy of its video on an origin server.
2. The CDN runs edge servers in many locations — data centres in major cities, and sometimes inside internet providers’ networks.
3. When you press play, you’re routed to a nearby edge server, usually through DNS or a shared address that the network answers at the nearest location.
4. If the edge server already has the video segments you need, it serves them from its cache. If not, it fetches them from the origin (or another layer of the CDN) and keeps a copy for the next viewer.

Because modern streaming protocols deliver video as small segments over ordinary web technology, CDNs can cache and serve them efficiently. See streaming protocols explained.

On-demand vs live delivery

• On-demand: popular titles stay cached at the edge, so most viewers get them from a nearby server.
• Live: new segments are created every few seconds and pushed through the CDN as fast as possible. Thousands of viewers then fetch the same fresh segments from their local edges. Waiting for each segment is one reason live streams run behind broadcast TV.

CDNs inside internet providers

Some large streaming services place cache servers inside internet providers’ networks, so popular video never has to cross the wider internet at all. Arrangements between streaming services, CDNs and internet providers (known as peering and interconnection) affect how smooth streaming is on different providers.

CDNs vs multicast

Broadband providers’ own TV services often use multicast inside their managed networks instead: one stream per channel, copied where needed. CDNs do a similar job for the open internet, using caching and many servers rather than network-level copying. Our guide to multicast IPTV explains the difference.

Why streaming quality can still vary

Even with CDNs, performance depends on the whole path:

• Your home network — Wi-Fi at the TV is the most common weak link.
• Your internet provider’s network — especially at busy evening hours.
• The connection between your provider and the CDN — some routes are better than others.
• The edge server’s load — during huge live events, edges can be stretched.
• Cache misses — unpopular content may need fetching from further away the first time.

That’s why two households on different internet providers can have different experiences with the same service, and why tests at the TV matter. Our guide to testing internet speed for streaming shows how to check your side of the path.

Multi-CDN

Large streaming services often use several CDNs at once, steering viewers to whichever performs best in their area at that moment, and switching automatically if one has problems. It’s invisible to viewers but improves reliability, especially during big live events.

What it means for you

• Fast start-up and fewer stalls, because content is nearby.
• Big live events usually work because load is spread across many servers.
• Evening slowdowns are still possible, from congestion anywhere in the chain.
• Your home network still matters most in many cases — a nearby CDN can’t fix weak Wi-Fi.

How to tell where a slowdown is happening

You can’t see inside a CDN, but you can narrow a problem down with a few simple checks:

1. Try another service at the same time. If every app is slow, the problem is probably your home network or your internet provider. If only one service struggles, the issue is more likely on that service’s delivery path.
2. Test at the TV, not the router. Run a speed test on the streaming device itself, or on a phone held next to it. A fast result at the router and a slow one at the TV points to Wi-Fi.
3. Compare wired and wireless. Plug the device into the router with a cable for a few minutes. If the stream improves, the CDN was never the bottleneck.
4. Note the time of day. Problems that appear only at peak evening hours and disappear later suggest congestion somewhere along the route.
5. Check the service’s status page or social channels during big live events, when edge servers are busiest.

If the problem consistently affects one service on one internet provider, report it to both. Providers and streaming services can adjust routing and capacity, but only if they know where the trouble is.

Caching, freshness and why new episodes sometimes start slowly

Edge servers keep popular content and drop rarely watched items to make space. A brand-new episode at release time, or an older title few people watch, may not yet be cached near you. The first viewers in an area then wait slightly longer while the edge fetches segments from further away; after that, everyone nearby gets them locally. Services often pre-position big releases on edge servers in advance to avoid exactly this.

A worked example

Two neighbours watch the same live final on the same service. One, whose internet provider hosts the service’s cache servers locally, gets smooth HD all evening; the other, on a provider with a congested route to the CDN, sees quality drops at half-time when demand peaks. Both have strong Wi-Fi — the difference is the path between their provider and the CDN.

The bottom line

CDNs keep copies of video close to viewers, so streams start fast and scale to huge audiences. They can’t fix weak Wi-Fi or a congested route, but they’re the reason modern streaming works at all — and a big part of why performance can differ between internet providers.