What is CDN peering and why is it important?

CDN peering is the practice of establishing direct network connections between a CDN provider and other networks, typically Internet Service Providers, cloud platforms, or other content networks. Instead of routing traffic through third-party transit providers, which adds latency and costs money per gigabit, peered networks exchange traffic directly at shared interconnection points. For CDN providers, peering is critical because it reduces delivery latency by eliminating intermediate network hops, lowers operating costs by avoiding transit fees that range from 0.50 to 5.00 dollars per Mbps per month, and improves reliability by removing dependency on third-party networks that may experience congestion or outages.

What is an Internet Exchange Point (IXP)?

An Internet Exchange Point is a physical facility where multiple networks connect their infrastructure to exchange traffic directly with each other. An IXP provides a shared switching fabric, usually a large Ethernet switch or set of switches, that allows any connected network to peer with any other connected network at that location. IXPs dramatically reduce the cost of interconnection because a single port connection gives access to hundreds or thousands of potential peering partners. The largest IXPs, such as DE-CIX Frankfurt with over 1,100 connected networks and peak traffic exceeding 14 Tbps, serve as critical infrastructure for the global internet by enabling efficient traffic exchange at regional hubs.

What is the difference between settlement-free peering and paid transit?

Settlement-free peering is an arrangement where two networks agree to exchange traffic at no cost to either party, based on the mutual benefit of direct connectivity. This works when both networks send and receive roughly equal volumes of traffic. Paid transit is a commercial arrangement where one network pays another to carry its traffic and provide access to the broader internet. Transit providers connect to many other networks and effectively sell reachability. CDN providers strongly prefer settlement-free peering because their traffic volumes are massive. A CDN delivering 100 Tbps of content would pay millions in monthly transit fees, whereas peering at an IXP costs only the port fee, typically 500 to 5,000 dollars per month regardless of traffic volume.

How do CDN providers embed servers inside ISP networks?

CDN providers negotiate agreements with ISPs to place cache servers directly inside the ISP data centers or central offices. The CDN provides the hardware and software at no cost to the ISP. In return, the ISP benefits from reduced upstream transit costs because popular content is served locally rather than fetched from external networks. The CDN benefits from being as close as possible to end users, typically achieving sub-5ms latency for cached content. Akamai operates over 4,200 server locations in more than 1,400 networks through this model. Netflix Open Connect similarly places custom storage appliances inside ISP networks, serving over 95 percent of Netflix traffic locally and reducing the ISP transit bill substantially.

How many IXPs does a typical CDN connect to?

The number of IXP connections varies dramatically by CDN provider size and strategy. Small or regional CDN providers may connect to 5-20 IXPs in their primary service regions. Mid-size providers like Bunny CDN or KeyCDN typically connect to 30-80 IXPs. Large global providers maintain far more connections: Cloudflare peers at over 330 IXPs worldwide, Akamai connects at hundreds of IXPs plus direct private interconnections with over 1,400 networks, and Fastly peers at approximately 100 IXPs. The general strategy is to connect at every IXP where significant traffic exchange justifies the port cost, which is typically any IXP where the provider exchanges more than 1 Gbps of sustained traffic with networks present at that facility.

CDN Peering and Internet Exchange Points Explained

March 1, 2026 · Alex Petrov · 9 min read

CDN peering is the practice of establishing direct network connections between CDN providers and other networks—ISPs, cloud platforms, and enterprise networks—to exchange traffic without routing through third-party transit providers. Internet Exchange Points (IXPs) are the physical facilities where these connections happen at scale. Together, peering and IXPs form the interconnection layer that determines how efficiently content travels from CDN edge servers to end users, directly affecting latency, cost, and reliability.

What Is Network Peering and How Does It Work?

Network peering is a direct interconnection between two autonomous systems (networks with their own BGP routing) that allows them to exchange traffic without paying a third-party transit provider. When two networks peer, they agree to carry each other traffic across their respective infrastructures at no per-bit cost.

Figure 1: Global CDN Distribution — Points of Presence worldwide

The internet is built on two fundamental interconnection models:

Transit: Paying for Reachability

Transit is a paid relationship where a customer network pays a provider network to carry its traffic and provide access to the rest of the internet. The transit provider announces the customer routes to its own peers and upstream providers, making the customer reachable globally. Transit pricing ranges from $0.50 to $5.00 per Mbps per month, depending on volume, location, and market conditions.

For a CDN delivering 50 Tbps of traffic globally, transit costs at even $0.50/Mbps would exceed $25 million per month. This economic reality makes peering essential for CDN viability.

Peering: Direct Exchange

Peering eliminates the transit middleman. Two networks connect directly and exchange traffic destined for each other networks (and their customers) at no per-bit cost. The only costs are the physical infrastructure: cross-connect cables, router ports, and any IXP port fees.

Peering comes in two forms:

Public peering — Networks connect at an IXP using a shared switching fabric, enabling many-to-many interconnection through a single port
Private peering (PNI) — Two networks run a dedicated cross-connect cable between their routers, typically in the same data center or across a metro fiber link

CDN providers use both: public peering at IXPs for the breadth of connectivity (reaching hundreds of networks through one port), and private peering for high-volume relationships where a dedicated connection capacity is needed.

What Are Internet Exchange Points and Why Do CDNs Use Them?

An Internet Exchange Point is a physical facility that provides shared switching infrastructure where multiple networks interconnect. Rather than each network building private interconnections with every other network individually (which would require N-squared cross-connects), an IXP lets any connected network peer with any other connected network through a single port.

Performance Comparison: Edge vs Origin Processing
Metric	Edge Processing	Origin Processing	Improvement
Latency (p50)	8–15 ms	120–300 ms	15–20x faster
Cache Hit Ratio	85–95%	N/A	Reduces origin load
TLS Handshake	1–5 ms (nearby PoP)	50–150 ms	10–30x faster
Bandwidth Cost	$0.01–0.04/GB	$0.05–0.12/GB	3–5x cheaper
Availability	99.99% (multi-PoP)	99.9% (single DC)	10x fewer outages

Inside an IXP

The core of an IXP is a high-capacity Ethernet switching platform, typically running at 100 Gbps or 400 Gbps per port. Connected networks each have a router with a port on this shared fabric. BGP (Border Gateway Protocol) sessions between routers establish which IP prefixes each network will accept from the other, defining the scope of their peering relationship.

Major IXPs also provide:

Route servers — Automated BGP session management that establishes peering with all participants through a single session, reducing configuration overhead
Looking glass tools — Diagnostic interfaces that show routing tables and reachability from the IXP perspective
Traffic statistics — Real-time and historical traffic volume data per port and per peer
Reseller ports — Smaller port sizes (1 Gbps, 10 Gbps) that allow smaller networks to participate without committing to 100 Gbps ports

Major IXPs by Traffic Volume

IXP	Location	Peak Traffic	Connected Networks	Port Sizes
DE-CIX Frankfurt	Frankfurt, Germany	14+ Tbps	1,100+	1G - 400G
AMS-IX	Amsterdam, Netherlands	12+ Tbps	900+	1G - 400G
LINX	London, UK	8+ Tbps	950+	1G - 400G
IX.br (PTT-SP)	Sao Paulo, Brazil	15+ Tbps	2,500+	1G - 400G
Equinix IX Ashburn	Ashburn, Virginia, USA	5+ Tbps	300+	10G - 100G
JPNAP	Tokyo, Japan	4+ Tbps	250+	1G - 100G

CDN providers connect at IXPs because one 100 Gbps port (costing roughly $2,000-$5,000 per month) provides access to hundreds of ISP networks. The alternative—buying transit from a Tier 1 carrier—would cost 10-100 times more for the same traffic volume. Learn more about how this infrastructure integrates into overall CDN architecture.

How Do CDNs Reduce Transit Costs Through Peering?

CDN economics are dominated by bandwidth costs. The more traffic a CDN can exchange through peering rather than transit, the lower its per-gigabyte delivery cost. Major CDN providers have systematically built peering relationships to minimize their transit dependency.

The Peering Ratio

The peering ratio measures what percentage of a network total outbound traffic is exchanged via peering versus paid transit. Mature CDN providers aim for peering ratios above 90%, meaning less than 10% of their traffic incurs transit fees.

Cloudflare — Peers at 330+ IXPs and maintains 12,500+ direct peering sessions, achieving an estimated peering ratio above 95%
Akamai — Connects at hundreds of IXPs plus 1,400+ embedded network deployments, with effectively 98%+ peered traffic
Fastly — Peers at approximately 100 IXPs with a focus on high-capacity private interconnections at strategic locations

Cost Impact Analysis

Consider a CDN delivering 10 Tbps of sustained traffic (approximately 3.2 exabytes per month):

Scenario	Monthly Cost Estimate	Per-GB Cost
100% paid transit at $0.50/Mbps	$5,000,000	$0.00156
70% peered, 30% transit	$1,600,000	$0.00050
95% peered, 5% transit	$350,000	$0.00011

The difference between 70% and 95% peering saves $1.25 million per month. This explains why CDN providers invest heavily in peering infrastructure and why CDN pricing varies significantly between providers with different peering ratios.

What Is ISP-Embedded CDN Infrastructure?

Beyond peering at IXPs, some CDN providers take interconnection a step further by placing cache servers directly inside ISP networks. This model, sometimes called "deep embedding" or "last-mile CDN," positions content as close as possible to end users.

Figure 2: CDN Provider Feature Comparison

How ISP Embedding Works

The CDN provider negotiates an agreement with an ISP to deploy servers in the ISP data center or central office. The CDN provides:

Cache server hardware (typically 1U or 2U servers with 50-200 TB of SSD storage)
Management software and monitoring
Content provisioning and cache warming
Hardware maintenance and replacement

The ISP provides:

Rack space and power (typically 1-4 kW per server)
Network connectivity to their internal backbone
BGP routing integration to attract user traffic to the local cache

Both parties benefit: the CDN achieves sub-5ms latency to users on that ISP network, while the ISP reduces expensive upstream transit because popular content stays local. A large ISP can save millions annually in transit costs by hosting CDN appliances.

Providers Using ISP Embedding

Akamai — Over 4,200 locations in 1,400+ networks worldwide, the most extensive embedded deployment of any CDN
Netflix Open Connect — Custom storage appliances (OCAs) deployed in ISP networks globally, serving 95%+ of Netflix traffic locally
Google GGC (Global Cache) — Cache nodes offered to ISPs to serve YouTube, Google Play, and other Google content locally
Meta FNA — Facebook Network Appliances deployed in ISP facilities to cache Facebook, Instagram, and WhatsApp content

These embedded deployments represent the deepest tier of CDN network topology, sitting below the traditional edge PoPs in the cache hierarchy.

How Do CDN Peering Policies Work?

Not every network can freely peer with a CDN provider. Peering policies define the criteria networks must meet to establish a direct interconnection. CDN providers typically maintain three categories:

Open Peering

The network will peer with any other network that meets basic technical requirements (BGP-capable router, valid ASN, minimum port size). Cloudflare follows an open peering policy, welcoming any network regardless of size. This strategy maximizes peering ratio at the cost of managing many small-volume sessions.

Selective Peering

The network peers only with networks that meet traffic volume or geographic presence requirements. Many traditional CDN providers require minimum sustained traffic exchange of 500 Mbps to 1 Gbps before establishing peering. This focuses engineering effort on high-value interconnections.

Restrictive Peering

The network limits peering to specific networks based on strategic value, typically Tier 1 carriers and large eyeball networks. Some large content providers use restrictive peering to maintain negotiating leverage with ISPs.

For networks wanting to peer with CDN providers, the standard process involves registering on PeeringDB (the global peering directory), joining mutual IXPs, and sending a peering request to the CDN provider NOC (Network Operations Center).

How Does Peering Affect CDN Latency and Performance?

The interconnection strategy directly impacts the latency users experience. Each network hop between a CDN edge server and the user adds 1-15ms of latency depending on the hop type:

Same facility (IXP cross-connect) — Under 1ms added latency
Same metro (private peering across facilities) — 1-3ms added latency
Regional transit hop — 5-15ms added latency
Long-haul transit hop — 20-80ms added latency (coast-to-coast or international)

A CDN with direct peering at an IXP where the user ISP is also connected eliminates all transit hops. The traffic path becomes: user → ISP network → IXP fabric → CDN edge server, with total network latency under 5ms. Without peering, the same request might traverse: user → ISP → ISP transit provider → CDN transit provider → CDN edge, adding 20-50ms.

This latency difference explains why CDN latency optimization starts with interconnection strategy. The fastest cache server in the world cannot compensate for a suboptimal network path. Providers with denser peering at IXPs and more Points of Presence consistently deliver lower TTFB across diverse user populations.

What Are the Emerging Trends in CDN Interconnection?

CDN interconnection continues to evolve as traffic volumes grow and new deployment models emerge:

400 GbE adoption — IXPs and private peering are migrating from 100 Gbps to 400 Gbps ports, driven by video streaming growth and AI model distribution
Edge compute peering — CDN edge compute services require not just content peering but also compute interconnection with cloud providers for hybrid workloads
Submarine cable CDN — CDN providers are colocating PoPs at submarine cable landing stations to intercept intercontinental traffic at the earliest possible point
Private backbone expansion — Major CDNs increasingly use private fiber networks between PoPs, reducing dependence on shared transit even for inter-PoP traffic

Understanding peering and IXP interconnection is essential for evaluating CDN providers. A provider with dense peering at regional IXPs will consistently outperform one with fewer connections, regardless of their edge server capabilities. When comparing providers with different routing strategies, always consider their interconnection breadth alongside their PoP count and cache capacity.