A content delivery network, or CDN, is a geographically distributed system of servers that stores copies of web files and delivers them from a location close to the person requesting them. It exists because distance and congestion slow the internet down. A page, script or video segment fetched from a single server in Virginia reaches a reader in Frankfurt more slowly, and less reliably, than the same bytes served from a machine a few kilometres away. For advertisers and publishers, the CDN is often the layer that decides whether a landing page loads, a tag fires or a video ad starts on time.

How a request reaches the edge

Three components do the work. The origin server holds the master copy of a site. Edge servers, grouped into points of presence (PoPs), hold cached copies. A routing system steers each visitor to a suitable edge.

Routing takes two main forms. Akamai relies on the Domain Name System (DNS): a customer points www.example.com at an edge hostname such as www.example.com.edgesuite.net through a CNAME record, and Akamai's name servers return the IP address of the best edge server for that user, according to Akamai's technical documentation. Cloudflare uses anycast, announcing the same IP address from many data centres and letting the Border Gateway Protocol (BGP) carry each request to the nearest location with capacity, according to its CDN reference architecture.

What happens next is mechanical. At Cloudflare, connections terminate at an HTTP and Transport Layer Security (TLS) layer, pass through a core proxy that applies each customer's rules, then reach a component that performs a cache lookup or fetches the file from origin. A stored, valid copy produces a cache hit. Anything else is a cache miss, which adds a round trip and loads the origin.

Freshness is governed by headers defined in RFC 9111, the Internet Engineering Task Force (IETF) caching standard published in June 2022. A response carrying Cache-Control: public, max-age=86400, s-maxage=3600 lets a browser reuse a file for 24 hours, while a shared cache such as a CDN must revalidate after one hour, because s-maxage applies only to shared caches and takes precedence there. RFC 9213, published the same month, added a CDN-Cache-Control field so publishers can set CDN-specific rules without touching other caches.

Billing is driven mostly by bytes leaving the edge. Amazon CloudFront's list rate for North America and Europe starts at $0.085 per gigabyte for the first 10 terabytes a month, after a free terabyte, and falls to $0.020 above five petabytes, according to AWS rates compiled by EgressCost in August 2026.

Where it sits in the advertising stack

Publishers are the heaviest users on the sell side. Pages, images, header bidding scripts and video all move through CDNs. In server-side ad insertion (SSAI), the CDN treats the insertion service as the manifest origin, so a million concurrent viewers generate a million distinct playlists. Google Ad Manager's Dynamic Ad Insertion (DAI) requires CDN configurations with separate ingest and delivery URL prefixes, supports only the Akamai model for token authentication, and lets a player choose among several CDNs at session start through a dai-dlid parameter, according to Google's help documentation. For live streams, Google also allows ad segments to travel through an external CDN that uses Google's Ad CDN as origin, arguing that a shared connection avoids a "thundering herd" of requests when a break begins.

The buy side met CDNs through measurement. Google's tag gateway for advertisers routes Google tags through a path on the advertiser's own domain, launching with Cloudflare as its first CDN partner and an 11% signal improvement reported by early adopters. Akamai followed on January 29, 2026, and Fastly launched its version on April 8, 2026, citing a 14% uplift drawn from seven days of Google data in April 2025. Because the proxy hides the visitor's connection, Google needs location passed in headers such as X-Forwarded-CountryRegion to keep regional reporting and consent defaults accurate.

CDN logs have become a data source in their own right. Microsoft Clarity's AI bot reporting depends on server-side log collection through CDN integrations, and Microsoft warned that connecting them may add provider charges.

Origins and evolution

The problem was posed before the product existed. In early 1995 Tim Berners-Lee challenged colleagues at the Massachusetts Institute of Technology (MIT) to find a better way to deliver web content, according to Akamai. Tom Leighton, a professor of applied mathematics, and Danny Lewin, who joined him in 1996, developed algorithms to route and replicate content across distributed servers, incorporating Akamai on August 20, 1998. Its first live traffic, in February 1999, was a pixel buried in the Disney site. Commercial service began that April, with Yahoo as a charter customer.

Cloud providers arrived later. Amazon Web Services launched CloudFront in November 2008. By September 2012 network operators were deploying their own CDNs, and the IETF's RFC 6707 noted that no open specifications existed for interconnecting them. Programmability came next: Cloudflare announced Workers, which runs JavaScript on edge servers, on September 29, 2017, and opened it to all customers on March 13, 2018. By June 2022 Optimizely was moving experiment decisions from the browser to the CDN.

Market share concentrated. W3Techs data put Cloudflare in front of around 20% of all websites in November 2025, against between 1% and 2% for CloudFront, according to Statista.

Why it matters to marketing

Speed shows up in measurable outcomes. Cloudflare's analysis of 9 billion data points found 91.7% of pages served from cache achieved a good time-to-first-byte rating, against 79.7% when origin processing was required. Both figures come from Cloudflare itself.

The CDN is also a chokepoint that governments and regulators act upon. Russian internet providers began throttling Cloudflare-protected sites to 16 kilobytes per connection on June 9, 2025. Italy's communications regulator fined Cloudflare EUR 14 million under its Piracy Shield blocking system, and the company appealed on March 8, 2026. Crawler access, long expressed in robots.txt files, is increasingly enforced at the edge instead.

Where CDNs fail

Shared infrastructure fails in shared ways. On June 8, 2021, a valid configuration change by a single Fastly customer triggered a bug introduced in a May 12 deployment, and 85% of Fastly's network returned errors. Within 49 minutes 95% was operating normally, according to the company. "Even though there were specific conditions that triggered this outage, we should have anticipated it," wrote Nick Rockwell, Fastly's senior vice president of engineering and infrastructure at the time.

Cloudflare's failure on November 18, 2025 was broader. A database permissions change at 11:05 UTC doubled the size of a Bot Management feature file, which breached a 200-feature limit (about 60 were in use) and crashed the proxy. Core traffic was largely restored by 14:30 and all systems by 17:06, according to chief executive Matthew Prince, who called it the company's worst outage since 2019. "Given Cloudflare's importance in the Internet ecosystem any outage of any of our systems is unacceptable," he wrote.

Script-hosting CDNs carry supply-chain risk. After Funnull acquired the polyfill.io domain in February 2024, security firm Sansec reported on June 25, 2024 that it was injecting malware into more than 100,000 sites. Cloudflare suggested tens of millions, according to Censys, and the estimates were never reconciled. Google began blocking Google Ads for e-commerce sites loading the script, Sansec reported.

Automated traffic strains the economics. Cloudflare and ETH Zurich reported that AI crawler traffic lowers cache hit rates, since independent crawler instances appear as new visitors. First-party routing is contested too: AdGuard and EasyPrivacy filter lists began naming server-side tagging subdomains in May 2026.

Not the same as

Origin server or web host. The origin stores and generates content; the CDN caches and relays it. Google Ad Manager's DAI preparation guide blurs the distinction by describing the CDN as "the origin server" for digital content.

Ad server. An ad server chooses the creative and records the impression. A CDN only delivers the files, even when one company, as with Google's DAI, operates both.

Reverse proxy and WAF. A CDN is a specialised reverse proxy, but not every reverse proxy caches at global scale. W3Techs classifies Cloudflare under reverse proxy services, and web application firewall (WAF), distributed denial-of-service (DDoS) mitigation and bot management run on the same request path.

Edge computing. Caching returns stored bytes. Edge compute platforms such as Workers execute code on the same servers.

Recent developments

Cloudflare has turned its network into a policy layer for AI crawlers. Pay per crawl launched in private beta on July 1, 2025, using HTTP 402 responses. A year later the company moved toward paying publishers when content appears in an answer and set September 15, 2026 as the date from which Training and Agent crawlers are blocked by default on ad-carrying pages for newly onboarded domains. Its dashboard shows crawl-to-referral ratios from 118 to nearly 50,000, and on August 21, 2026 it added Bot Preference Sync and a separate training default for ad-monetised domains.

Other vendors are building on the same layer. When Clarity added robots.txt violation detection on June 23, 2026, administrators had to connect Fastly, CloudFront or Cloudflare. Fastly joined Experian's Agent Trust ecosystem on July 24, 2026, moving AI agent verification to the edge. Tag gateway reached general availability on Google Cloud on June 1, 2026, shortly after an update let advertisers hide GTM container IDs.

Small operators feel the arithmetic most directly. PatronView runs on roughly $90 a month of Cloudflare Workers with edge caching, a bill that rose about 500% during one period of heavy scraping.

Timeline

  • Early 1995: Tim Berners-Lee challenges MIT colleagues to find a better way to deliver web content
  • August 20, 1998: Tom Leighton and Danny Lewin incorporate Akamai
  • February 1999: Akamai delivers its first live traffic, a pixel on the Disney site
  • April 1999: Akamai launches commercial service with Yahoo as a charter customer
  • November 2008: Amazon Web Services launches CloudFront
  • September 2012: The IETF publishes RFC 6707 on CDN interconnection
  • September 29, 2017: Cloudflare announces Workers for running code on edge servers
  • March 13, 2018: Workers becomes available to all Cloudflare customers
  • June 8, 2021: A Fastly bug leaves 85% of its network returning errors
  • June 2022: The IETF publishes RFC 9111 on HTTP caching and RFC 9213 on targeted cache control
  • February 2024: Funnull acquires the polyfill.io domain
  • June 25, 2024: Sansec reports polyfill.io malware on more than 100,000 sites
  • May 8, 2025: Google tag gateway for advertisers reaches general availability with Cloudflare
  • June 9, 2025: Russian internet providers begin throttling Cloudflare-protected sites to 16 kilobytes
  • July 1, 2025: Cloudflare opens pay per crawl in private beta
  • November 18, 2025: Cloudflare suffers its worst outage since 2019
  • December 29, 2025: Italy's AGCOM fines Cloudflare EUR 14 million under Piracy Shield
  • January 29, 2026: Akamai becomes a tag gateway CDN partner
  • April 8, 2026: Fastly launches Ad Tag Gateway
  • June 1, 2026: Tag gateway reaches general availability on Google Cloud
  • June 23, 2026: Microsoft Clarity ties robots.txt violation detection to CDN connections
  • July 1, 2026: Cloudflare shifts from per-crawl charging toward per-answer payments
  • July 24, 2026: Fastly joins Experian's Agent Trust ecosystem
  • August 21, 2026: Cloudflare publishes Bot Preference Sync
  • September 15, 2026: Default blocking of Training and Agent crawlers begins for new Cloudflare domains carrying ads

Summary

Who: CDN operators including Akamai, Cloudflare, Fastly and Amazon CloudFront run the networks. Publishers use them for pages, scripts and video, advertisers for landing pages and tag routing, and ad platforms such as Google Ad Manager for ad and stream delivery. Regulators, browser makers, ad blockers and AI crawler operators increasingly act on the same layer.

What: A geographically distributed system of servers that caches copies of web content and serves them from locations near users, steered by DNS or anycast routing and governed by HTTP caching headers defined in RFC 9111 and RFC 9213.

When: Conceived after Tim Berners-Lee's 1995 challenge at MIT, commercialised by Akamai in April 1999, extended by cloud providers from 2008, made programmable from 2017, and repositioned since 2025 as a control point for measurement and AI crawler access.

Where: In points of presence spread across hundreds of cities, sitting between the visitor's browser or app and the origin server that holds the master copy of the content.

Why: Distance and congestion slow delivery, and a single origin cannot absorb traffic spikes or attacks alone. That same position in front of a large share of the web concentrates risk, as the Fastly and Cloudflare outages showed, and gives CDN operators growing influence over what crawlers, tags and ad blockers can reach.