• Home
• ask.DrPeering Blog
• About
• Contact

A Study of 28 Peering Policies

The following are snippets of Peering Policy Clauses found in the Peering Rules of the Road - A Study of 28 Peering Policies study. Clauses were categorized and put into rough categories for comparison.

Traffic Volume Peering Policy Clause

Traffic Volume Requirements

1.1.2 Minimum utilization: The peering Candidate must have a minimum aggregate of 50 Mbps and a maximum of 200 Mbps on any single peering exchange. – AboveNet, Public Peering

Traffic Volume. The aggregate amount of traffic exchanged in each direction over all interconnection links between the Requester and the Verizon Business Internet Network with which it desires to interconnect shall equal or exceed 1500 Mbps of traffic for Verizon Business-US, 150 Mbps of traffic for Verizon Business-Europe, and 30 Mbps of traffic for Verizon Business-ASPAC. – Verizon

For the purposes of Requirements 1.2 and 1.4 of the Policy, the traffic to be measured will include only what is being exchanged by the two Internet Networks and their respective customers (excluding any transit traffic) in the specific geographic region for which settlement-free interconnection has been requested. – Verizon

Traffic requirements: The AVERAGE traffic volume exchanged between ATDN and Applicant must be 972 Mbps or higher in each direction (inbound and outbound). – ATDN

At least 5 Mbps of aggregate traffic, measured using 95th Percentile in either direction, must be exchanged on an ongoing basis. Specific exemptions on traffic levels may be made, at Internap's discretion. – InterNAP

for Public Peering At least 50 Mbps of aggregate traffic, measured using 95th Percentile in either direction, must be exchanged on an ongoing basis. Specific exemptions on traffic levels may be made, at Internap's discretion. – InterNap

Aggregate traffic over the peering sessions should have a combined measurement (Ingress + Egress @ 95th percentile) of at least 350M for Public Peering. – TW Telecom

Aggregate traffic over the peering sessions should have a combined measurement (Ingress + Egress @ 95th percentile) of at least 500M for Private Peering. – TW Telecom

[Will not peer if…]Existing traffic levels are below 1Mbps peak – EasyNet [Will normally peer if Existing traffic levels are at 100Mbps or more – EasyNet

For private peering, a minimum of 20 Mb/s average or 40 Mb/s 95th percentile sustained traffic over the three (3) immediately preceeding months is required to have been exchanged between the two potential peer networks. For public peering, there are no traffic requirements. – HopOne

A minimum Internet traffic exchange of 10Mbps (95th percentile) with Autonomous system 22773. – Cox

for Public Peering A minimum Internet traffic exchange of 100Mbps (95th percentile) with Autonomous System 22773. Cox, for Private Peering

# Domestic public peers must sustain a minimum of 150 mbit/s of aggregate traffic based on 95th percentile calculations. –wbsconnect

# International public peers must sustain a minimum of 50 mbit/s of aggregate traffic based on 95th percentile calculations. – wbsconnect

# Any public peer sustaining in excess of 500mbit/s, domestic or international, must agree to peer privately with interconnection costs to be shared by both parties. – wbsconnect

# Private peers must sustain a minimum of 500 mbit/s of aggregate traffic based on 95th percentile calculations. Both parties shall maintain enough capacity on private interconnection ports to ensure delivery of traffic within normal SLA standards. – wbsconnect

# A minimum of 100 Mbps busy-hour traffic exchange is required (25 Mbps for international networks). – Mzima

Applicant's traffic to/from the Comcast network must be on-net only and must amount to at least 7 Gbps peak in the dominant direction. Interconnection bandwidth must be at least 10 Gbps at each interconnection point. – Comcast

Applicant has a minimum traffic from the TISCALI Network of 1 Gbit/sec - judged on 95th percentile over 1 (one) month (this may be proofed with a test peering). This is a mandatory requirement. – tinet

Aggregated average traffic between LambdaNet and Peer shall be at least 20 mbps. – LambdaNet for Public Peering # LambdaNet requires 50 mbps of aggregated average traffic to justify a private peering relationship. – LambdaNet

for Private Peering # Have a total minimum busy hour traffic exchange of 50Mbps with New Edge Networks' AS – NewEdge Must maintain a minimum traffic exchange of 200Mbps (95th percentile) with AS20115 – Charter

Potential peer must be able to demonstrate usage history with an aggregate peak average usage rate greater than 70 Megabits/s or sustain an average of 4.32 Terabits/day; bi-directionally. Whichever is applicable. – Cablevision

At least 250Mb/s of aggregate traffic measured at peak times must be exchanged. Public NorthAmerica, At least 125Mb/s of aggregate traffic measured at peak times must be exchanged. For Europe, At least 125Mb/s of aggregate traffic measured at peak times must be exchanged. – Global, Private Peering

At least 500Mb/s of aggregate traffic measured at peak times must be exchanged in North America., At least 500Mb/s of aggregate traffic measured at peak times must be exchanged. In Europe, At least 500Mb/s of aggregate traffic measured at peak times must be exchanged for global peering. – WVFiber

Peer's traffic to/from the interconnected AT&T US network must be on-net only and must amount to at least 3 Gbps peak in the dominant direction for peers of AS7018. At least 200 Mbps peak in the dominant direction will be required to be considered for public peering with AS7132. – AT&T