Operational Requirements:

• Each Network shall operate a fully staffed Network Operations Center that is available 24 hours a day, 7 days a week, regardless of holidays or other special events.

• Each Network shall provide Network Abuse point(s) of contact responsible for tracking SPAM, hacking, Denial of Service, and other network security and abuse issues, providing a knowledgeable technician within a two-hour period after notice.

• Each Network is expected to have network security measures in place to thwart Denial of Service attacks.

• Each Network must operate a fully redundant network, capable of handling a simultaneous single-node outage in each network without significantly affecting the performance of the traffic being exchanged.

• Neither party shall establish a static route, a route of last resort, or otherwise send traffic to the other party for a route not announced via BGP.

• Neither party shall alter, sell, or otherwise provide next-hops of the other party to a third party. Such offences shall be seen as a major violation of the policy, subject to immediate termination of the agreement.

• The Requester must maintain a PeeringDB record containing up-to-date contacts and technical specifications.

• The Requester must maintain an Internet Routing Registry AS-MACRO, providing accurate information on the prefixes which may be announced.

• The Requester must RPKI sign their originated routes.

• 2degrees will reject invalid and unknown RPKI routes.

Interconnection Requirements:

• The Requester shall maintain a fully redundant backbone network, in which most inter-hub links have a capacity of at least 10Gb.

Infrastructure Requirements:

• The Requester shall maintain a fully redundant backbone network, in which most inter-hub links have a capacity of at least 10Gb.

Traffic Exchange Volume:

• The aggregate volume of traffic exchanged in each direction over all interconnect links between the Requester and 2degrees shall equal or exceed 1Gbps, as measured on a 95th Percentile (95P) basis over a 7-day period.

Traffic Exchange Balance:

• The ratio of the aggregate amount of traffic exchanged between the Requester and 2degrees shall be roughly balanced and shall not exceed 2:1.

The peering policy is only a guideline. Meeting or exceeding all of the above requirements does not guarantee 2degrees will enter into a peering relationship with the Interconnection Candidate.

Existing peering arrangements will have their status reviewed periodically to ensure capacity is sufficient for growth, contacts are refreshed for operations purposes, and all criteria continue to be met.

Meeting the general qualifications is not a guarantee that a peering relationship with 2degrees will be established. 2degrees will evaluate several business factors and reserves the right not to enter into a peering agreement with an otherwise qualified applicant and additionally reserves the right to waive any of the qualifications set forth above.

2degrees reserves the right to terminate peering with established peers who do not meet the criteria described above.

Periodic reviews of the policies contained here will be conducted to ensure that the criteria and eligibility requirements are consistent with 2degrees' business needs. 2degrees may modify this peering policy at any time.