Peering
View on WikipediaIn computer networking, peering is a voluntary interconnection of administratively separate Internet networks for the purpose of exchanging traffic between the "down-stream" users of each network. Peering is settlement-free, also known as "bill-and-keep" or "sender keeps all", meaning that neither party pays the other in association with the exchange of traffic; instead, each derives and retains revenue from its own customers.
An agreement by two or more networks to peer is instantiated by a physical interconnection of the networks, an exchange of routing information through the Border Gateway Protocol (BGP), tacit agreement to norms of conduct and, in some extraordinarily rare cases (0.07%), a formalized contractual document.[1][2]
In 0.02% of cases the word "peering" is used to describe situations where there is some settlement involved. Because these outliers can be viewed as creating ambiguity, the phrase "settlement-free peering" is sometimes used to explicitly denote normal cost-free peering.[3]
History
[edit]The first Internet exchange point was the Commercial Internet eXchange (CIX), formed by Alternet/UUNET (now Verizon Business), PSI, and CERFNET to exchange traffic without regard for whether the traffic complied with the acceptable use policy (AUP) of the NSFNet or ANS' interconnection policy.[4] The CIX infrastructure consisted of a single router, managed by PSI, and was initially located in Santa Clara, California. Paying CIX members were allowed to attach to the router directly or via leased lines. After some time, the router was also attached to the Pacific Bell SMDS cloud. The router was later moved to the Palo Alto Internet Exchange, or PAIX, which was developed and operated by Digital Equipment Corporation (DEC). Because the CIX operated at OSI layer 3, rather than OSI layer 2, and because it was not neutral, in the sense that it was operated by one of its participants rather than by all of them collectively, and it conducted lobbying activities supported by some of its participants and not by others, it would not today be considered an Internet exchange point. Nonetheless, it was the first thing to bear that name.
The first exchange point to resemble modern, neutral, Ethernet-based exchanges was the Metropolitan Area Ethernet, or MAE, in Tysons Corner, Virginia. When the United States government de-funded the NSFNET backbone, Internet exchange points were needed to replace its function, and initial governmental funding was used to aid the preexisting MAE and bootstrap three other exchanges, which they dubbed NAPs, or "Network Access Points," in accordance with the terminology of the National Information Infrastructure document.[5] All four are now defunct or no longer functioning as Internet exchange points:
- MAE-East – Located in Tysons Corner, Virginia, and later relocated to Ashburn, Virginia
- Chicago NAP – Operated by Ameritech and located in Chicago, Illinois
- New York NAP – Operated by Sprint and located in Pennsauken, New Jersey
- San Francisco NAP – Operated by PacBell and located in the Bay Area
As the Internet grew, and traffic levels increased, these NAPs became a network bottleneck. Most of the early NAPs utilized FDDI technology, which provided only 100 Mbit/s of capacity to each participant. Some of these exchanges upgraded to ATM technology, which provided OC-3 (155 Mbit/s) and OC-12 (622 Mbit/s) of capacity.
Other prospective exchange point operators moved directly into offering Ethernet technology, such as gigabit Ethernet (1,000 Mbit/s), which quickly became the predominant choice for Internet exchange points due to the reduced cost and increased capacity offered. Today, almost all significant exchange points operate solely over Ethernet, and most of the largest exchange points offer 10, 40, and even 100 gigabit service.
During the dot-com boom, many exchange point and carrier-neutral colocation providers had plans to build as many as 50 locations to promote carrier interconnection in the United States alone. Essentially all of these plans were abandoned following the dot-com bust, and today it is considered both economically and technically infeasible to support this level of interconnection among even the largest of networks.
How peering works
[edit]The Internet is a collection of separate and distinct networks referred to as autonomous systems, each one consisting of a set of globally unique IP addresses and a unique global BGP routing policy.
The interconnection relationships between Autonomous Systems are of exactly two types:
- Peering - Two networks exchange traffic between their users freely, and for mutual benefit.
- Transit – One network pays another network for access to the Internet.
Therefore, in order for a network to reach any specific other network on the Internet, it must either:
- Sell transit service to that network or a chain of resellers ending at that network (making them a 'customer'),
- Peer with that network or with a network which sells transit service to that network, or
- Buy transit service from any other network (which is then responsible for providing interconnection to the rest of the Internet).
The Internet is based on the principle of global or end-to-end reachability, which means that any Internet user can transparently exchange traffic with any other Internet user. Therefore, a network is connected to the Internet if and only if it buys transit, or peers with every other network which also does not purchase transit (which together constitute a "default free zone" or "DFZ").
Public peering is done at Internet exchange points (IXPs), while private peering can be done with direct links between networks.[6][7]
Motivations for peering
[edit]Peering involves two networks coming together to exchange traffic with each other freely, and for mutual benefit.[8][9] This 'mutual benefit' is most often the motivation behind peering, which is often described solely by "reduced costs for transit services". Other less tangible motivations can include:
- Increased redundancy (by reducing dependence on one or more transit providers).
- Increased capacity for extremely large amounts of traffic (distributing traffic across many networks).
- Increased routing control over one's traffic.
- Improved performance (attempting to bypass potential bottlenecks with a "direct" path).
- Improved perception of one's network (being able to claim a "higher tier").
- Ease of requesting for emergency aid (from friendly peers).
Physical interconnections for peering
[edit]

The physical interconnections used for peering are categorized into two types:
- Public peering – Interconnection utilizing a multi-party shared switch fabric such as an Ethernet switch.
- Private peering – Interconnection utilizing a point-to-point link between two parties.
Public peering
[edit]Public peering is accomplished across a Layer 2 access technology, generally called a shared fabric. At these locations, multiple carriers interconnect with one or more other carriers across a single physical port. Historically, public peering locations were known as network access points (NAPs). Today they are most often called exchange points or Internet exchanges ("IXP"). Many of the largest exchange points in the world can have hundreds of participants, and some span multiple buildings and colocation facilities across a city.[10]
Since public peering allows networks interested in peering to interconnect with many other networks through a single port, it is often considered to offer "less capacity" than private peering, but to a larger number of networks. Many smaller networks, or networks which are just beginning to peer, find that public peering exchange points provide an excellent way to meet and interconnect with other networks which may be open to peering with them. Some larger networks utilize public peering as a way to aggregate a large number of "smaller peers", or as a location for conducting low-cost "trial peering" without the expense of provisioning private peering on a temporary basis, while other larger networks are not willing to participate at public exchanges at all.
A few exchange points, particularly in the United States, are operated by commercial carrier-neutral third parties which often are data centers, which are critical for achieving cost-effective data center connectivity.[11]
Private peering
[edit]Private peering is the direct interconnection between only two networks, across a Layer 1 or 2 medium that offers dedicated capacity that is not shared by any other parties. Early in the history of the Internet, many private peers occurred across "telco" provisioned SONET circuits between individual carrier-owned facilities. Today, most private peering interconnections occur at carrier hotels data centers[12] or carrier neutral colocation facilities, where a direct crossconnect (private network interconnect, PNI) can be provisioned between participants within the same building, usually for a much lower cost than telco circuits. Colocation centers often host private peering connections between their customers, internet transit providers and cloud providers.[13][14] meet-me rooms for connecting customers together[15] Internet exchange points,[16][17] and landing points and terminal equipment for fiber optic submarine communication cables,[18] connecting the internet.[19]
Most of the traffic on the Internet, especially traffic between the largest networks, occurs via private peering. However, because of the resources required to provision each private peer, many networks are unwilling to provide private peering to "small" networks, or to "new" networks which have not yet proven that they will provide a mutual benefit.
Peering agreement
[edit]Throughout the history of the Internet, there have been a spectrum of kinds of agreements between peers, ranging from handshake agreements to written contracts as required by one or more parties. Such agreements set forth the details of how traffic is to be exchanged, along with a list of expected activities which may be necessary to maintain the peering relationship, a list of activities which may be considered abusive and result in termination of the relationship, and details concerning how the relationship can be terminated. Detailed contracts of this type are typically used between the largest ISPs, as well as the ones operating in the most heavily regulated economies. As of 2011, such contracts account for less than 0.5% of all peering agreements.[1]
Depeering
[edit]By definition, peering is the voluntary and free exchange of traffic between two networks, for mutual benefit. If one or both networks believes that there is no longer a mutual benefit, they may decide to cease peering: this is known as depeering. Some of the reasons why one network may wish to depeer another include:
- A desire that the other network pay settlement, either in exchange for continued peering or for transit services.
- A belief that the other network is "profiting unduly" from the no-settlement interconnection.
- Concern over traffic ratios, which is related to the fair sharing of cost for the interconnection.
- A desire to peer with the upstream transit provider of the peered network.
- Abuse of the interconnection by the other party, such as pointing default or utilizing the peer for transit.
- Instability of the peered network, repeated routing leaks, lack of response to network abuse issues, etc.
- The inability or unwillingness of the peered network to provision additional capacity for peering.
- The belief that the peered network is unduly peering with one's customers.
- Various external political factors (including personal conflicts between individuals at each network).
In some situations, networks which are being depeered have been known to attempt to fight to keep the peering by intentionally breaking the connectivity between the two networks when the peer is removed, either through a deliberate act or an act of omission. The goal is to force the depeering network to have so many customer complaints that they are willing to restore peering. Examples of this include forcing traffic via a path that does not have enough capacity to handle the load, or intentionally blocking alternate routes to or from the other network. Some notable examples of these situations have included:
- BBN Planet vs Exodus Communications[20]
- PSINet vs Cable & Wireless[21]
- AOL Transit Data Network (ATDN) vs Cogent Communications[22]
- France Telecom vs Cogent Communications[23]
- France Telecom (Wanadoo) vs Proxad (Free)[24]
- Level 3 Communications vs XO Communications[25]
- Level 3 Communications vs Cogent Communications[26]
- Telecom/Telefónica/Impsat/Prima vs CABASE (Argentina) [27]
- Cogent Communications vs TeliaSonera[28]
- Sprint-Nextel vs Cogent Communications[29]
- SFR vs OVH[30]
- The French ISP 'Free' vs YouTube[31]
Modern peering
[edit]Donut peering model
[edit]The "donut peering" model[32] describes the intensive interconnection of small and medium-sized regional networks that make up much of the Internet.[1] Traffic between these regional networks can be modeled as a toroid, with a core "donut hole" that is poorly interconnected to the networks around it.[33]
As detailed above, some carriers attempted to form a cartel of self-described Tier 1 networks, nominally refusing to peer with any networks outside the oligopoly.[1] Seeking to reduce transit costs, connections between regional networks bypass those "core" networks. Data takes a more direct path, reducing latency and packet loss. This also improves resiliency between consumers and content providers via multiple connections in many locations around the world, in particular during business disputes between the core transit providers.[34][35]
Multilateral peering
[edit]The majority of BGP AS-AS adjacencies are the product of multilateral peering agreements, or MLPAs.[1] In multilateral peering, an unlimited number of parties agree to exchange traffic on common terms, using a single agreement to which they each accede. The multilateral peering is typically technically instantiated in a route server or route reflector (which differ from looking glasses in that they serve routes back out to participants, rather than just listening to inbound routes) to redistribute routes via a BGP hub-and-spoke topology, rather than a partial-mesh topology. The two primary criticisms of multilateral peering are that it breaks the shared fate of the forwarding and routing planes, since the layer-2 connection between two participants could hypothetically fail while their layer-2 connections with the route server remained up, and that they force all participants to treat each other with the same, undifferentiated, routing policy. The primary benefit of multilateral peering is that it minimizes configuration for each peer, while maximizing the efficiency with which new peers can begin contributing routes to the exchange. While optional multilateral peering agreements and route servers are now widely acknowledged to be a good practice, mandatory multilateral peering agreements (MMLPAs) have long been agreed to not be a good practice.[36]
Peering locations
[edit]The modern Internet operates with significantly more peering locations than at any time in the past, resulting in improved performance and better routing for the majority of the traffic on the Internet.[1] However, in the interests of reducing costs and improving efficiency, most networks have attempted to standardize on relatively few locations within these individual regions where they will be able to quickly and efficiently interconnect with their peering partners.
Exchange points
[edit]As of 2021, the largest exchange points in the world are Ponto de Troca de Tráfego Metro São Paulo, in São Paulo, with 2,289 peering networks; OpenIXP in Jakarta, with 1,097 peering networks; and DE-CIX in Frankfurt, with 1,050 peering networks.[37] The United States, with a historically larger focus on private peering and commercial public peering, has much less traffic visible on public peering switch-fabrics compared to other regions that are dominated by non-profit membership exchange points. Collectively, the many exchange points operated by Equinix are generally considered to be the largest, though traffic figures are not generally published. Other important but smaller exchange points include AMS-IX in Amsterdam, LINX and LONAP in London, and NYIIX in New York.
URLs to some public traffic statistics of exchange points include:
|
|
|
|
|
|
Peering and BGP
[edit]A great deal of the complexity in the BGP routing protocol exists to aid the enforcement and fine-tuning of peering and transit agreements. BGP allows operators to define a policy that determines where traffic is routed. Three things are commonly used to determine routing: local-preference, multi exit discriminators (MEDs) and AS-Path. Local-preference is used internally within a network to differentiate classes of networks. For example, a particular network will have a higher preference set on internal and customer advertisements. Settlement free peering is then configured to be preferred over paid IP transit.
Networks that speak BGP to each other can engage in multi exit discriminator exchange with each other, although most do not. When networks interconnect in several locations, MEDs can be used to reference that network's interior gateway protocol cost. This results in both networks sharing the burden of transporting each other's traffic on their own network (or cold potato). Hot-potato or nearest-exit routing, which is typically the normal behavior on the Internet, is where traffic destined to another network is delivered to the closest interconnection point.
Law and policy
[edit]Internet interconnection is not regulated in the same way that public telephone network interconnection is regulated.[38] Nevertheless, Internet interconnection has been the subject of several areas of federal policy in the United States. Perhaps the most dramatic example of this is the attempted MCI Worldcom/Sprint merger. In this case, the Department of Justice blocked the merger specifically because of the impact of the merger on the Internet backbone market (thereby requiring MCI to divest itself of its successful "internetMCI" business to gain approval).[39] In 2001, the Federal Communications Commission's advisory committee, the Network Reliability and Interoperability Council recommended that Internet backbones publish their peering policies, something that they had been hesitant to do beforehand[citation needed]. The FCC has also reviewed competition in the backbone market in its Section 706 proceedings which review whether advanced telecommunications are being provided to all Americans in a reasonable and timely manner.
Finally, Internet interconnection has become an issue in the international arena under something known as the International Charging Arrangements for Internet Services (ICAIS).[40] In the ICAIS debate, countries underserved by Internet backbones have complained that it is unfair that they must pay the full cost of connecting to an Internet exchange point in a different country, frequently the United States. These advocates argue that Internet interconnection should work like international telephone interconnection, with each party paying half of the cost.[41] Those who argue against ICAIS point out that much of the problem would be solved by building local exchange points. A significant amount of the traffic, it is argued, that is brought to the US and exchanged then leaves the US, using US exchange points as switching offices but not terminating in the US.[42] In some worst-case scenarios, traffic from one side of a street is brought all the way to a distant exchange point in a foreign country, exchanged, and then returned to another side of the street.[43] Countries with liberalized telecommunications and open markets, where competition between backbone providers occurs, tend to oppose ICAIS.[citation needed]
See also
[edit]References
[edit]- ^ a b c d e f Woodcock, Bill; Adhikari, Vijay (2 May 2011). "Survey of Characteristics of Internet Carrier Interconnection Agreements" (PDF). Packet Clearing House. Archived from the original (PDF) on 10 June 2015. Retrieved 5 May 2011.
- ^ Woodcock, Bill; Frigino, Marco (21 November 2016). "Survey of Characteristics of Internet Carrier Interconnection Agreements" (PDF). Packet Clearing House. Retrieved 28 May 2021.
Of the total analyzed agreements, 1,347 (0.07%) were formalized in written contracts. This is down from 0.49% in 2011. The remaining 1,934,166 (99.93%) were "handshake" agreements in which the parties agreed to informal or commonly understood terms without creating a written document.
- ^ Woodcock, Bill; Frigino, Marco (21 November 2016). "Survey of Characteristics of Internet Carrier Interconnection Agreements" (PDF). Packet Clearing House. Retrieved 28 May 2021.
Of the agreements we analyzed, 1,935,111 (99.98%) had symmetric terms, in which each party gave and received the same conditions as the other. Only 403 (0.02%) had asymmetric terms, in which the parties gave and received conditions with specifically defined differences, and these exceptions were down from 0.27% in 2011. Typical examples of asymmetric agreements are ones in which one of the parties compensates the other for routes that it would not otherwise receive (sometimes called "paid peering" or "on-net routes"), or in which one party is required to meet terms or requirements imposed by the other ("minimum peering requirements"), often concerning volume of traffic or number or geographic distribution of interconnection locations.
- ^ "Internet History :: Era of Disruption & Competition: CIX". Cybertelecom, Federal Internet Law & Policy. Archived from the original on 12 June 2021. Retrieved 30 March 2022.
- ^ Ford, Peter; Aiken, B.; Braun, H.W. (February 2004). "NSF implementation plan for interim NREN". Journal on High Speed Networking, 1993.
- ^ Information Network Engineering. 株式会社 オーム社. 20 July 2015. ISBN 978-4-274-99991-8.
- ^ Sunyaev, Ali (12 February 2020). Internet Computing: Principles of Distributed Systems and Emerging Internet-Based Technologies. Springer. ISBN 978-3-030-34957-8.
- ^ nowaybackbot. "What is peering & why networks peer". peer.org.uk. Retrieved 11 February 2022.
- ^ "DrPeering International - Top 4 Motivations to Peer".
- ^ "Internet Exchange Directory". Packet Clearing House.
- ^ Cosmano, Joe (2009), Choosing a Data Center (PDF), Disaster Recovery Journal, retrieved 21 July 2012[dead link]
- ^ "Data Center Tours: Equinix DC12, Ashburn, Virginia | Data Center Frontier". www.datacenterfrontier.com. Retrieved 25 August 2025.
- ^ "Touring the PhoenixNAP Data Center - Page 2 of 5 - ServeTheHome". www.servethehome.com. Retrieved 25 August 2025.
- ^ "The rise and rebirth of carrier hotels - DCD". Archived from the original on 6 November 2023. Retrieved 25 August 2025.
- ^ Dave Bullock (3 April 2008). "A Lesson in Internet Anatomy: The World's Densest Meet-Me Room". Wired. Retrieved 16 June 2022.
- ^ "AWASR, AMS-IX, and Alliance Networks launch Internet exchange in Oman - DCD". Archived from the original on 6 December 2023. Retrieved 25 August 2025.
- ^ "Data Center Tours: Equinix DC12, Ashburn, Virginia | Data Center Frontier". www.datacenterfrontier.com. Retrieved 25 August 2025.
- ^ "How the Internet works: Submarine fiber, brains in jars, and coaxial cables - Ars Technica". arstechnica.com. Retrieved 25 August 2025.
- ^ "Equinix Expands Miami Data Center Key to Latin American Connectivity". www.datacenterknowledge.com. Retrieved 25 August 2025.
- ^ John Curran (30 November 2010). "Ratios and Peering". Retrieved 9 July 2011.
- ^ Burton, Graeme (7 June 2001). "PSINet-C&W dispute causes Internet blackout". Information Age. Archived from the original on 27 September 2007. Retrieved 28 September 2006.
- ^ Noguchi, Yuki (27 December 2002). "'Peering' Dispute With AOL Slows Cogent Customer Access". Washington Post. Retrieved 28 September 2006.
- ^ Kuri, Jürgen; Smith, Robert W. (21 April 2005). "France Telecom severs all network links to competitor Cogent". Heise online. Archived from the original on 8 September 2006. Retrieved 28 September 2006.
- ^ Le Bouder, Gonéri (11 January 2003). "Problème de peering entre Free et France Télécom" (in French). LinuxFr. Retrieved 28 September 2006.
- ^ "Level 3 and XO Communications Sign Settlement-Free Peering Agreement". PR Newswire. 7 January 2013. Retrieved 17 January 2024.
- ^ Cowley, Stacey (6 October 2005). "ISP spat blacks out Net connections". InfoWorld. Archived from the original on 8 January 2007. Retrieved 28 September 2006.
- ^ "CABASE sale aireada del conflicto NAP".
- ^ Malik, Om (14 March 2008). "The Telia-Cogent Spat Could Ruin the Web For Many – GigaOM". Gigaom. Archived from the original on 18 March 2008.
- ^ Ricknäs, Mikael (31 October 2008). "Sprint-Cogent Dispute Puts Small Rip in Fabric of Internet". PC World. Retrieved 31 October 2008.[dead link]
- ^ Guillaume, Nicolas (12 February 2011). "INTERCONNEXION RÉSEAUX : OVH ET SFR CALMENT LE JEU" (in French). ITespresso. Retrieved 12 February 2011.
- ^ Fradin, Andréa (15 January 2013). "Pourquoi ça rame quand je veux regarder une vidéo YouTube avec Free". Slate (in French). Retrieved 15 January 2013.
- ^ Woodcock, Bill (13 January 2003). "Internet Topology and Economics: How Supply and Demand Influence the Changing Shape of the Global Network" (ppt). lecture at the University of Minnesota Digital Technology Center. Packet Clearing House. Retrieved 28 April 2011.
- ^ "Changing Role of Peering & Transit in IP Network Interconnection Economics" (PDF). Cook Report on Internet. XI (8–9). Cook Network Consultants. November–December 2002. ISSN 1071-6327. Archived from the original (PDF) on 19 July 2011. Retrieved 28 April 2011.
- ^ Kirkwood, Grant (September 2009). "The 'Donut Peering' Model: Optimizing IP Transit for Online Video" (PDF). Archived from the original (PDF) on 16 November 2009. Retrieved 2 October 2009.
- ^ Mohney, Doug (4 September 2009). "A Deep Dive Into IP Voice Peering". IP Communications. Technology Marketing Corporation. Retrieved 4 September 2009.
- ^ "Internet Exchange Point Policy Documents: Layer 3 participant technical requirements: Mandatory multi-lateral peering". Packet Clearing House. Archived from the original on 9 August 2014. Retrieved 4 October 2013.
- ^ "Packet Clearing House - Internet Exchange Point Directory". pch.net. Packet Clearing House. 28 May 2021. Retrieved 28 May 2021.
- ^ Woodcock, Bill; Weller, Dennis (29 January 2013). "Internet Traffic Exchange: Market Developments and Policy Challenges" (PDF). OECD Digital Economy Papers. 207. OECD. doi:10.1787/5k918gpt130q-en. Archived (PDF) from the original on 8 August 2021.
The performance of the Internet market model contrasts sharply with that of traditional regulated forms of voice traffic exchange. If the price of Internet transit were stated in the form of an equivalent voice minute rate, it would be about USD 0.0000008 per minute—five orders of magnitude lower than typical voice rates. This is a remarkable and under-recognised endorsement of the multi-stakeholder, market driven nature of the Internet.
- ^ "Justice Departments Clears WorldCom/MCI Merger after MCI Agrees to Sell its Internet Business". Archived from the original on 1 June 2009.
- ^ Internet Traffic Exchange and the Development of End to End International Telecommunication Competition, OECD 3/25/02
- ^ "ITU-T Recommendation D.50".
- ^ CAIDA: Internet Measurement: Myths about Internet data (5 December 2001)
- ^ Woodcock, Bill; Edelman, Benjamin (12 September 2012). "Toward Efficiencies in Canadian Internet Traffic Exchange" (PDF). Canadian Internet Registration Authority and Packet Clearing House. Archived from the original (PDF) on 25 August 2013. Retrieved 20 October 2013.
External links
[edit]- PeeringDB: A free database of peering locations and participants
- The peering Playbook (PDF): Strategies of peering networks Archived 8 October 2011 at the Wayback Machine
- Example Tier 1 Peering Requirements: AT&T (AS7018)
- Example Tier 1 Peering Requirements: AOL Transit Data Network (AS1668) Archived 15 December 2017 at the Wayback Machine
- Example Tier 2 Peering Requirements: Entanet (AS8468) Archived 4 June 2023 at the Wayback Machine
- Cybertelecom :: Backbones – Federal Internet Law and Policy
- How the 'Net works: an introduction into Peering and Transit, Ars Technica
Peering
View on GrokipediaDefinition and Fundamentals
Core Concept of Peering
Peering constitutes the voluntary interconnection between two or more administratively separate autonomous systems (ASes) on the Internet, enabling the direct exchange of traffic destined for each other's customers without monetary settlement.[11][5] This settlement-free arrangement contrasts with paid transit services, where one network compensates another for broader Internet reachability, and operates on the principle of mutual benefit, typically requiring roughly balanced traffic volumes to justify the absence of payments.[12][13] By establishing direct links, peering minimizes reliance on intermediary networks, thereby reducing latency, packet loss, and operational costs for participating entities such as Internet service providers (ISPs), content delivery networks (CDNs) like Netflix and Cloudflare, cloud providers like AWS, and large enterprises. Effective peering ensures low latency and high speeds, while poor peering arrangements can lead to routing detours, bottlenecks, and degraded performance for specific services.[1] At its foundation, peering leverages Border Gateway Protocol (BGP) announcements to advertise routes and forward traffic bilaterally between peers, often facilitated through physical cross-connects in colocation facilities or via shared infrastructure at Internet exchange points (IXPs).[11] Networks evaluate peering viability based on factors including traffic ratios—ideally close to 1:1 to ensure reciprocity—and potential for cost avoidance, as peering eliminates transit fees that can exceed millions annually for high-volume operators.[13][12] For instance, a content-heavy network like a video streaming service may peer with eye-ball networks (those serving end-users) to offload outbound traffic efficiently, optimizing global reach without upstream dependencies.[1] The core incentive for peering stems from economic and performance efficiencies: it localizes traffic exchange, averting the higher costs and delays of routing through third-party transit providers, which charge based on port capacity and data volume.[5] Empirical analyses indicate that peering can reduce end-to-end latency by 20-50 milliseconds compared to transit paths, enhancing user experience for applications sensitive to delay, such as real-time communications.[14] However, peering agreements remain selective, with networks often declining connections that would result in net traffic outflow without reciprocal value, preserving incentives for balanced participation.[13] This framework underpins the Internet's decentralized architecture, fostering scalability as traffic volumes have grown exponentially since the 1990s.[1]Distinction from Transit and Other Interconnections
Internet Protocol (IP) transit involves a customer network paying a provider for access to the entire Internet, where the provider advertises a full routing table and carries traffic bidirectionally to and from global destinations.[15] In contrast, peering constitutes a settlement-free bilateral agreement between two autonomous systems (ASes) to exchange traffic solely destined for each other's networks or direct customers, without extending reachability to the broader Internet. This limited scope in peering means participants announce only their own prefixes and those of their immediate downstream customers via Border Gateway Protocol (BGP), avoiding the propagation of full Internet routes that characterizes transit.[16] Economically, transit operates on a paid model where the customer compensates the provider based on bandwidth usage or flat rates, enabling smaller networks to leverage the provider's upstream connections for universal connectivity.[17] Peering, however, eschews monetary exchange under ideal conditions, relying on roughly balanced traffic ratios—typically within a 1:1 to 2:1 inbound-to-outbound limit—to ensure mutual benefit without one party subsidizing the other.[18] Violations of balance can lead to renegotiation, de-peering, or conversion to paid peering, where one network compensates the other for disproportionate traffic carriage.[19] Technically, peering interconnections prioritize direct, low-latency paths, often yielding superior performance over transit routes for inter-network traffic, as evidenced by studies showing peering paths outperform transit for approximately 91% of ASes in terms of latency and path length.[20] Transit, by routing through multiple upstream providers, introduces additional hops and potential congestion points, though it guarantees default-free routing to all Internet destinations.[14] Other interconnection variants, such as multilateral peering at Internet Exchange Points (IXPs), extend settlement-free exchange to multiple participants simultaneously but retain the core limitation of non-transitive reachability, distinguishing them from transit's comprehensive forwarding obligation.[21] These distinctions underpin peering's role in optimizing costs and efficiency for traffic between comparable networks, while transit serves as the foundational mechanism for universal Internet attachment.[22]Historical Development
Origins in ARPANET and Early Internet
The ARPANET, launched on October 29, 1969, by the U.S. Department of Defense's Advanced Research Projects Agency (ARPA), represented the foundational packet-switched network that pioneered internetworking concepts. Initially comprising four nodes at UCLA, Stanford Research Institute, UC Santa Barbara, and the University of Utah, it expanded to connect over 200 hosts by the late 1970s, primarily serving military, academic, and research entities. Interconnections were handled via centralized Interface Message Processors (IMPs) and later gateways, but the network's design emphasized resource sharing among autonomous systems, laying groundwork for distributed connectivity without inherent commercial transit models.[23] The emergence of peering as settlement-free interconnection arose in the early 1980s amid restrictions on ARPANET access, limited to government and contractors, which excluded broader academic computer science communities. The National Science Foundation (NSF)-sponsored Computer Science Network (CSNET), operational from July 1, 1981, addressed this by linking over 180 sites via diverse media including ARPANET gateways, phone lines, and X.25 networks. The first documented peering, as traced by networking pioneer Lyman Chapin, occurred between ARPANET and CSNET during this era; lacking authority for paid transit, operators established direct links without accounting or settlement to enable traffic exchange and avoid bureaucratic delays. This bilateral, non-monetary arrangement—exchanging roughly equal traffic volumes—defined peering's core principle of mutual benefit without payment.[24][25] By the mid-1980s, the NSFNET backbone, activated in 1986 at 56 kbps and upgraded to T1 speeds by 1988, interconnected 13 initial regional networks serving supercomputing centers and universities, integrating with ARPANET (fully transitioned to TCP/IP by January 1, 1983) and CSNET through similar settlement-free gateways. These links, managed by entities like Merit Network for NSFNET, relied on emerging Border Gateway Protocol (BGP) precursors and Exterior Gateway Protocol (EGP) for routing announcements, fostering a federated internet architecture. Peering thus evolved from ad hoc necessities in resource-constrained, government-funded environments, prioritizing operational efficiency over economic settlement, with traffic volumes balanced to justify no-fee exchanges—typically under informal ratios like 1:1.[26][25]Commercialization in the 1990s
In the early 1990s, the push for commercial Internet access led to the creation of dedicated exchange points for peering outside government-subsidized networks. The Commercial Internet Exchange (CIX), formed in 1991 by network service providers such as Alternet, PSI, and CERFNET, provided a multilateral platform for settlement-free traffic exchange, circumventing the NSFNET's Acceptable Use Policy that barred commercial use.[27] This arrangement allowed participating providers to interconnect directly via a shared router in Santa Clara, California, fostering initial commercial scalability without reliance on paid transit or federal infrastructure.[27] To manage the anticipated growth post-NSFNET, the National Science Foundation issued solicitation NSF 93-52 in 1993, outlining the establishment of Network Access Points (NAPs) as neutral peering facilities. Four such NAPs were deployed by 1995—operated by Sprint in New York, Ameritech in Chicago, Pacific Bell in California, and MFS in Washington, D.C.—to interconnect regional and national service providers during the transition.[27] These points emphasized open access and BGP-based routing for efficient, non-discriminatory peering, with initial capacities supporting T3 speeds (45 Mbps) to handle emerging commercial backbones from entities like MCI and Sprint.[24] The NSFNET backbone's decommissioning on April 30, 1995, marked the definitive commercialization of peering, shifting the Internet to private sector dominance where Tier 1 providers exchanged traffic via settlement-free agreements to minimize costs and latency.[28] This era saw rapid expansion of facilities like MAE-East, established in 1991 and scaling to multiple nodes by mid-decade, alongside bilateral private peering links that complemented public NAPs for high-volume pairs.[27] Peering volumes grew exponentially, with U.S. Internet traffic reaching approximately 1 Gbps aggregate by 1995, driven by incentives for networks of comparable size to avoid mutual transit fees.[24] However, as asymmetries emerged, selective peering policies began to formalize, laying groundwork for later disputes.[24]Expansion During the Dot-Com Era
The dot-com era, spanning roughly 1995 to 2000, witnessed explosive growth in internet adoption and content creation, with e-commerce sites, web portals, and early online services driving traffic volumes that necessitated expanded peering infrastructure to maintain performance and control costs. Major networks increasingly interconnected directly at existing Internet exchange points (IXPs), such as MAE-East (established in 1992 in the Washington, D.C. area), which saw heightened participation from ISPs and content providers like AOL and AT&T seeking low-latency exchanges amid surging demand.[29][30] This period marked a shift from limited, selective peering arrangements—often confined to a handful of network access points (NAPs) under NSFNET policies—to more widespread commercial interconnections, as the commercialization of the internet post-1995 encouraged bilateral and multilateral peering to bypass expensive transit fees.[4] Key expansions included the proliferation of IXP facilities in high-density locations, notably Ashburn, Virginia, where MAE-East's presence attracted colocation investments and became a nexus for peering due to its proximity to fiber optic hubs and federal policy incentives from the mid-1990s Telecommunications Act.[31] By the late 1990s, the number of operational IXPs worldwide had grown from fewer than a dozen in the early 1990s to several dozen, reflecting the dot-com-fueled buildout of dark fiber networks and data centers that enabled scalable peering points.[4] Innovations like Ethernet-based switching at IXPs, gaining traction over ATM by the late 1990s, further accelerated adoption by simplifying interconnections and reducing setup costs for emerging players.[29] Peering policies liberalized during this boom, with many Tier 1 and Tier 2 providers offering settlement-free peering to attract traffic and partners, leading to a rapid increase in direct interconnections—estimated to have multiplied as internet hosts grew from about 10 million in 1995 to over 100 million by 2000.[32] This expansion optimized routing efficiency for the era's asymmetric traffic patterns, dominated by web downloads, but also sowed seeds for post-bust reevaluations as overcapacity from speculative infrastructure investments became evident after the NASDAQ peak in March 2000.[29] Overall, the era's peering growth laid foundational infrastructure that supported the internet's resilience, even as the 2001 bust prompted consolidation among IXP operators and a return to more selective agreements.[32]Technical Mechanisms
Operational Principles of Peering
Operational principles of peering emphasize mutual benefit through direct traffic exchange, requiring balanced volumes to prevent free-riding and ensure cost efficiency. Networks establish peering only when aggregate value from reduced transit costs exceeds maintenance expenses, often formalized via settlement-free agreements contingent on traffic ratios not exceeding 1:3 inbound to outbound at the 95th percentile.[33][34] Monitoring occurs via NetFlow or similar tools during trial periods to verify shifts in traffic and costs before full commitment.[33] Technically, peering relies on Border Gateway Protocol (BGP) sessions over redundant interconnections, such as 10-100 Gigabit Ethernet links at public Internet Exchange Points (IXPs) or private facilities, with no advertisement of default routes or forwarding beyond announced prefixes.[34][35] Public peering at IXPs uses shared Layer 2 fabrics for multicast optional efficiency, while private peering demands direct cross-connects and dual BGP sessions for failover. Minimum traffic thresholds, such as 500 Mbps for exchange points or 2 Gbps for direct links, apply, with port upgrades triggered at 50-70% peak utilization to maintain performance.[1][35][34] Policies enforce no transit provision, prohibiting peered networks from routing third-party traffic without explicit consent, and require 24/7 network operations centers (NOCs) with updated profiles in databases like PeeringDB for coordination.[35][34] Violations, such as sustained imbalance or security lapses, prompt capacity reviews or de-peering trials to assess fitness without the link, prioritizing causal improvements in latency and cost over rigid ratios.[33] Multiple interconnection points—typically 2-6 per region—enhance redundancy and localize traffic, reducing end-to-end paths by up to 0.3 hops on average in value-optimized models.[34][33]Physical and Logical Interconnections
Physical interconnections for peering enable direct traffic exchange between autonomous systems (ASes) by linking their border routers via Ethernet cables to shared infrastructure. At Internet Exchange Points (IXPs), participants connect to a Layer 2 switch fabric, typically using copper or fiber optic ports rated at speeds from 1 Gbps to 100 Gbps or higher, allowing multiple networks to share the medium without dedicated pairwise cabling.[36] [37] This setup supports Ethernet framing for frame forwarding based on MAC addresses, with VLANs often used to segment peering LANs and prevent broadcast storms.[38] For private network interconnections (PNIs), ASes deploy dedicated physical links such as single-mode fiber or leased dark fiber directly between colocation facilities, bypassing shared fabrics for higher capacity and isolation.[39] [40] Logical interconnections overlay routing protocols on these physical paths to direct IP traffic. Peering ASes establish BGP sessions—TCP connections on port 179—over the Ethernet links, exchanging AS paths, prefixes, and attributes to announce reachable networks.[3] [41] In IXP environments, bilateral peering requires individual BGP sessions per counterpart, scaling poorly for large participant counts, whereas multilateral peering via route servers centralizes this: a single BGP session to the IXP's route server aggregates routes from all enabled peers, with the server reflecting updates but not forwarding data plane traffic.[42] [37] Route servers operate in the control plane only, relying on the underlying Layer 2 fabric for actual packet delivery based on learned MAC-IP mappings.[43] IXPs standardize on Layer 2 fabrics to maintain AS autonomy in Layer 3 decisions, avoiding centralized routing that Layer 3 IXPs impose, which can limit policy control and introduce single points of failure.[44] [45] Physical diversity, such as redundant cabling paths and multiple switch fabrics, mitigates outages, with interconnections often requiring single-mode fiber for long-haul or high-speed links exceeding 100 Gbps.[35]Integration with BGP Routing
Border Gateway Protocol (BGP) serves as the foundational mechanism for integrating peering arrangements into global internet routing, enabling autonomous systems (ASes) to exchange reachability information for IP prefixes directly between peers. In peering, external BGP (eBGP) sessions are established between border routers of distinct ASes over dedicated physical links or shared infrastructures like internet exchange points (IXPs), typically configured with a time-to-live (TTL) security value of 1 to enforce single-hop connectivity and mitigate spoofing risks.[46][47] These sessions facilitate the advertisement of network prefixes via BGP UPDATE messages, where each AS announces routes to destinations within its policy-defined scope, often the full internet routing table or selective subsets to optimize traffic symmetry and prevent imbalances.[46][3] Route selection in BGP peering relies on attributes such as AS_PATH length, which prevents loops by discarding announcements containing the receiver's own AS number, ensuring acyclic paths across peered networks. Peering policies, enforced through prefix-lists, AS-path filters, and communities, allow networks to control inbound and outbound traffic flows; for instance, peers may de-preference certain routes via LOCAL_PREF or MED adjustments to favor direct peering paths over transit alternatives, reducing latency and dependency on upstream providers.[46][48] This policy-driven approach contrasts with default-less routing in transit, as peering agreements often mandate mutual route leaking without payment, promoting efficient, settlement-free exchange while enabling rapid convergence—typically within seconds via BGP's incremental updates—compared to flooding protocols.[46][3] Empirical implementations demonstrate BGP's scalability in peering: at IXPs, route servers aggregate eBGP sessions to distribute routes from multiple participants without requiring full-mesh connectivity, as standardized in practices that prepend AS numbers or apply no-export communities to confine announcements.[48][47] Security extensions, such as TTL security (RFC 5082) and BGPsec (under development per RFC 8205 drafts), further harden peering sessions against hijacks, though adoption remains limited due to operational overhead.[46] Overall, BGP's integration empowers peering by decoupling routing decisions from monetary settlements, fostering a decentralized topology where ASes prioritize shortest AS_PATHs for mutual customer traffic, as evidenced by the protocol's role since BGP-4's standardization in 2006 (RFC 4271).[46][3]Economic Incentives
Motivations for Entering Peering Arrangements
Networks enter peering arrangements to minimize costs compared to purchasing internet transit services, where transit providers charge fees for routing traffic to destinations outside their network. Settlement-free peering allows direct traffic exchange without payments when volumes are roughly balanced, enabling ISPs to offload traffic that would otherwise incur transit expenses, particularly as customer bases and data demands expand.[49][50] Direct interconnections via peering reduce latency and improve end-to-end performance by shortening packet paths and avoiding intermediate transit hops, which can introduce delays, jitter, and higher packet loss rates. For instance, access ISPs peering with content networks deliver faster download speeds to residential users, enhancing user experience and retention without proportional increases in infrastructure spending.[51][52] Peering expands network reach by providing access to peer customers' address spaces without relying solely on transit providers, allowing ISPs to serve growing traffic volumes more scalably. This is especially beneficial for eye-ball networks (access providers) seeking content traffic and content delivery networks aiming for consumer audiences, fostering mutual growth in interconnected ecosystems.[13] Reliability gains from peering stem from diversified routing options, reducing single points of failure inherent in transit dependency; multiple peers act as backup paths during outages, maintaining service continuity.[51] Finally, peering confers competitive advantages, such as superior quality-of-service metrics that differentiate providers in saturated markets, where customers prioritize speed and uptime over price alone. Empirical analyses indicate that networks achieving balanced peering portfolios often realize 20-50% reductions in total connectivity costs while boosting throughput efficiency.[53][54]Cost Structures and Settlement Models
In settlement-free peering, networks interconnect without monetary exchange, assuming reciprocal benefits from balanced traffic flows, where each party independently bears the costs of physical and logical connections, such as colocation fees, cross-connect cabling, and Layer 2/3 port rentals at Internet Exchange Points (IXPs), typically ranging from $500 to $5,000 monthly per 10 Gbps port depending on the facility.[55][56] This model prevails when traffic ratios remain within thresholds like 2:1 inbound-to-outbound, minimizing incentives for payment by aligning costs with internalized savings from avoided transit fees, which can exceed $0.50–$2.00 per Mbps monthly in wholesale markets.[57][58] Paid peering introduces explicit financial settlements, where the network deriving asymmetric value—often content-heavy providers connecting to access-oriented ISPs—compensates the counterparty to cover disproportionate infrastructure utilization or secure lower-latency paths, with pricing models including volume-based tariffs (e.g., $0.10–$1.00 per Mbps for inbound traffic), capacity-based fees proportional to port speeds, or hybrid structures blending fixed and variable elements.[59][60] These arrangements offset the receiver's incremental operational costs, such as bandwidth provisioning and peering policy enforcement, while enabling the payer to bypass costlier transit routes; economic analyses show paid peering can reduce end-to-end costs by 20–50% relative to transit-only models under high-volume imbalances exceeding 10:1 ratios.[61][62]| Settlement Model | Key Cost Components | Allocation Mechanism | Typical Conditions for Viability |
|---|---|---|---|
| Settlement-Free | Internalized interconnection (ports, cross-connects, maintenance); no reimbursement | Each network self-funds based on own traffic contribution | Balanced volumes (e.g., <2:1 ratio); mutual transit avoidance benefits exceed setup OPEX/CAPEX[33][63] |
| Paid | Payer-funded compensation plus shared infra costs; volume or capacity tariffs | Directional payment from high-value sender to receiver, often covering 50–100% of induced costs | Imbalanced flows; payer gains from direct access efficiencies outweigh fees (e.g., content-to-eyeball scenarios)[59][64] |
Empirical Economic Impacts on Networks
Empirical analyses demonstrate that peering significantly lowers infrastructure costs compared to transit for many networks by enabling direct traffic exchange without intermediary fees. For example, a 10 Gbps peering port may cost approximately $1,700 per month, versus $10,000 per month for equivalent transit capacity, allowing networks to scale traffic volumes while minimizing upstream payments.[64] This cost differential incentivizes peering adoption, particularly as global internet traffic grows 40-50% annually, amplifying transit expenses despite per-unit price declines to around $0.45 per Mbps.[14] However, simulations reveal that up to 50% of network service providers experience net cost increases from peering if traffic diversion from revenue-generating transit links is not balanced, highlighting the need for strategic selectivity in agreements.[64] Peering also yields indirect economic benefits through enhanced performance, which correlates with reduced user churn and higher service value. Measurements across autonomous systems show peering paths outperforming transit in latency for 91% of cases, with median reductions to 6 IP hops versus 8 for transit, and propagation delay improvements exceeding 5% for 95% of networks.[14] Shorter paths (e.g., 3.7 hops under value-based peering policies versus 4.0 under traffic-ratio rules) further optimize bandwidth utilization, potentially increasing network fitness metrics by tens of thousands of dollars annually for stub and leaf providers in modeled scenarios.[33] These efficiencies compound at scale, as evidenced by correlations between peering location density and traffic volume growth, where networks expanding to multiple internet exchange points handle higher loads at lower marginal costs.[64] Notwithstanding these advantages, peering introduces network-wide externalities that can erode profitability for some participants. Agent-based models indicate that one network's peering expansion may cause 15% of others to lose customer traffic, with 10% experiencing utility declines—up to 50% in extreme cases—due to rerouted flows and competitive pressures forcing open policies.[64] Transit providers, in particular, see only 30% gaining from such shifts, as settlement-free peering diverts revenue streams.[64] Comprehensive surveys confirm peering reduces data exchange costs by 40-60% regionally, but outcomes vary by market maturity and negotiation leverage, underscoring that empirical gains are not universal without robust traffic balance assessments.[67]Agreement Frameworks
Negotiation and Types of Peering Agreements
Negotiation of peering agreements typically begins with prospective networks identifying complementary partners through analysis of traffic patterns, customer bases, and geographic reach, often using industry databases to assess compatibility and peering policies.[3] This evaluation prioritizes peers where traffic exchange would reduce latency, lower transit costs, and improve performance without significant imbalance, with networks exchanging data on autonomous system numbers, prefixes, and estimated volumes to gauge mutual value.[68] Initial contact occurs via email or events like NANOG meetings, followed by technical discussions on BGP session parameters, interconnection points, and capacity provisioning.[69] Commercial terms are then negotiated, emphasizing balanced traffic ratios—commonly requiring no more than a 2:1 inbound-to-outbound disparity over a 3-6 month rolling average—to prevent free-riding, alongside minimum port speeds (e.g., 10 Gbps or higher), SLAs for uptime (typically 99.99%), and monitoring protocols like MRTG or NetFlow for transparency.[70] Clauses address depeering triggers, such as sustained imbalance exceeding thresholds or policy violations, and may include non-disclosure agreements due to the proprietary nature of traffic data.[33] The process can span weeks to months, with larger networks imposing stricter criteria like no end-user competition or proven operational maturity, reflecting a value-based assessment where the peering link's net benefit justifies interconnection.[33] [3] Types of peering agreements include bilateral arrangements, where two networks directly negotiate terms for traffic exchange, often via private interconnections or at IXPs, tailored to specific traffic profiles and ratios.[71] Multilateral peering agreements (MLPAs), facilitated through IXP operators, enable multiple networks to interconnect via shared fabric without pairwise negotiations, relying on the IXP's master agreement for standardized rules on participation, fees, and dispute handling.[71] [1] These differ from selective policies, where networks limit peers to qualified candidates meeting size and quality benchmarks, versus open policies allowing broader access with minimal scrutiny, though formal agreements still govern operational details in both cases. Settlement-free agreements, predominant in balanced scenarios, contrast with paid variants where compensation applies for asymmetric benefits, but the former's negotiation focuses more on reciprocity than pricing.[72]Settlement-Free vs. Paid Peering
Settlement-free peering arrangements enable autonomous systems to interconnect and exchange customer traffic without monetary exchange, under the assumption of roughly balanced volumes that yield mutual economic value. This model, often termed "bill-and-keep," originated in the post-NSFNET era of the early 1990s, when newly commercialized Tier 1 providers sought to minimize costs by directly routing traffic rather than relying on paid transit.[73] Qualification typically requires traffic ratios below thresholds like 2:1 inbound-to-outbound, ensuring no single party bears disproportionate infrastructure costs, with violations prompting renegotiation or depeering.[74] Such agreements reduce dependency on upstream transit providers, lowering latency and expenses for participants with comparable eye-ball and content customer bases.[56] In contrast, paid peering imposes a financial obligation on one network—commonly the higher-traffic sender, such as a content provider—to compensate the recipient for interconnection access and capacity utilization. This variant technically mirrors settlement-free peering in routing customer-only traffic via BGP but incorporates payments to offset asymmetries, emerging prominently in the 2000s amid surging video traffic that strained traditional balances.[62] For example, U.S. providers like Comcast began offering paid peering options around 2008 to content distributors failing settlement-free criteria, pricing at transit-equivalent rates to cover port and backbone investments.[75] Similarly, in Europe, a 2012 case saw a Swiss ISP coerced by an incumbent to convert a settlement-free link to paid terms amid growing imbalances.[19] The divergence stems from causal economic dynamics: settlement-free peering thrives when reciprocal value—measured by avoided transit fees and traffic offload—equals out, incentivizing broad collaboration among symmetric networks, whereas paid peering addresses imbalances by internalizing costs, potentially enhancing quality through dedicated capacity but introducing bargaining frictions.[59] Empirical analyses indicate Internet access providers (IAPs) optimize by offering both, with settlement-free suiting low-congestion peers and paid ensuring revenue from high-volume asymmetric flows, though the latter risks inefficient overinvestment if payments exceed marginal costs.[76]| Aspect | Settlement-Free Peering | Paid Peering |
|---|---|---|
| Financial Settlement | None; assumes equal value exchange | Payment from one party (often sender) to recipient |
| Traffic Prerequisite | Balanced ratios (e.g., <2:1) for reciprocity | Handles imbalances; payment scales with volume |
| Primary Incentives | Cost savings via mutual offload; lower latency | Compensation for asymmetric burdens; premium QoS |
| Risk Factors | Depeering on imbalance detection | Negotiation disputes; potential for hold-up power |