Customer Portal

Search results

0

Your Choices Regarding Cookies on this Site

Welcome to retn.net. Cookies are important to the proper functioning of a site. To improve your experience, we use cookies collect statistics to optimize site functionality. Click Agree and proceed to accept cookies and go directly to the site or click on Learn more about our Cookie Policy and Privacy Policy to see details first.

Peering policy

TALK TO US
peering@retn.net

AS9002 peering policy

OVERVIEW

RETN owns and operates an IP network identified as Autonomous System 9002 with AS-RETN as-set (IPv4) and AS-RETN6 (IPv6).

Our IP network is directly interconnected with multiple ISPs, NSPs and CSPs. New peering connections are established, only when they are beneficial for RETN and its customers.

Below are the main principles which determine RETN’s decision regarding the benefits and appropriateness of establishing peering with potential partners.

RETN has a restrictive peering policy globally and considers each peering request based upon individual merits.

We reserve the right to reject a peering request or terminate existing peering relationships if their advantages are not evident to us.

BASIC REQUIREMENTS

Those who request private peering with RETN, whether over a PNI or IXP, should:

Have minimum traffic volumes of 20Gbps with RETN at each interconnection point (total minimum 60Gbps);


Establish interconnection with RETN in 3 separate mutually beneficial locations which are geographically separated by at least 2000km from each other;


Have balanced traffic with AS9002, with a minimum ratio of 50%;


Maintain a network consisting of fully redundant N x 100G links with each peering point or support 100G IP Ports for private interconnection;


Be able to react quickly to establish the additional capacity to meet traffic growth, and agree to upgrade connections at 70% utilisation;


Have implemented MANRS actions and be a participant of MANRS;


Maintain “full BGP view” at the edge router by means of BGPv4;


Announce only its own routes and the routes of its customers to AS9002, but not the routes received from other peers or upstream;


Not announce “martian” routes or the default route (0.0.0.0/0) to AS9002;


Manage a fully staffed 24×7 Network Operational Centre;


Provide its escalation matrix upon request in order to be able to quickly resolve possible network issues;


Agree RETN peering conditions in a formal interconnection agreement;


Be beneficial for RETN and our Customers.


Our PeeringDB page

Peering-DBPage

Procedure

If you wish to peer with AS9002, send us your request to peering@retn.net.

Please, provide your network description and technical details including:

ASN

As-set (as macro), if available

Type of traffic carried through your network

Depending on the traffic levels expected, peering interconnections can be set up as Private Network Interconnections (PNIs) or over public Internet Exchange Points (IXPs).

In case you do not meet the requirements of RETN’s peering policy, but take a strong interest in RETN’s IP transit service, please contact market@retn.net.