All tech news
Infrastructure5 min read

The Role of CDNs in Modern Web Infrastructure

How content delivery networks remove distance from a request, what they cost in concentration risk, and why they shape an ISP's traffic profile.

Neha Rakshitha
A content delivery network serving cached content from points of presence close to users.

A Content Delivery Network is a set of servers distributed across many locations that serve content from somewhere close to the person requesting it. The idea is simple and the consequences for how the internet is built are considerable.

The problem it solves

Without a CDN, every request travels to wherever the site is hosted. For a visitor on another continent that means a long round trip for each asset, and the delay is dominated by distance rather than by anything the server does.

A CDN copies content to servers in many places, and directs each request to a nearby one. The origin server is contacted only when the nearby copy does not have what was asked for.

How it works

Distribution. Content is copied to points of presence around the world. These hold cached copies of static assets: images, scripts, stylesheets, video segments and often whole pages.

Direction. A request is routed to a nearby point of presence, usually through DNS or through anycast routing that sends traffic to the closest instance of a shared address.

Cache hit or miss. If the local server holds a current copy it serves it immediately. If not, it fetches from the origin, serves the visitor, and keeps a copy for the next request.

Cache policy is where most of the engineering sits. How long a copy stays valid, how updates are pushed out, and what is too personalised to cache at all determine how much benefit the arrangement actually delivers.

What it provides

Lower latency, because distance is the dominant cost for most requests and the CDN removes most of it.

Reduced origin load, since the majority of requests never reach the origin server, which changes what capacity that server needs.

Resilience. Many locations mean one failing does not take the site down, and cached content can often continue to be served while an origin is unavailable.

Attack absorption. A distributed network with substantial capacity absorbs volumetric traffic that would overwhelm a single origin, which is why CDN and DDoS protection are frequently sold together.

Lower bandwidth cost for the origin, because the CDN serves the bulk of the traffic.

What it costs

The concentration is the concern. A small number of providers now sit in front of a very large share of the web, which means their failures are correlated across an enormous number of otherwise unrelated services. The Cloudflare outage of November 2025 demonstrated what that looks like in practice.

Cache invalidation is the persistent operational difficulty. Content that should have updated but has not is a common and confusing failure, and the more aggressive the caching the more often it happens.

Why an ISP cares

CDNs shape the traffic profile an operator carries. A large share of consumer traffic now originates from a relatively small number of CDN sources rather than from the whole internet evenly.

That has a direct consequence: it makes the traffic worth peering with or caching locally. Where a CDN has a presence at a local exchange, or will place a cache inside the operator's network, that traffic stops travelling over paid transit and starts being served from within the region. Both the cost and the latency improve at the same time, which is unusual.

Working out whether that is worth doing means knowing where traffic actually comes from. Flow records provide that, and it is generally the data that decides which peering and caching arrangements are worth pursuing. The broader picture is in internet exchange points.

CDNCachingLatencyPeering

Share this article

Run your ISP on one platform.

Subscribers, billing, provisioning and compliance in a single system.