Peering Policy

AS9002 peering policy


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.

RETN has a restrictive peering policy globally and considers each peering request based upon individual merits. Below are the main principles which determine RETN’s decision regarding the benefits and appropriateness of establishing peering with potential partners.

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 8Gbps with RETN;
• Have balanced traffic with AS9002, with a minimum ratio of 50%;
• Have implemented MANRS actions and be a participant of MANRS (;
• Secure a minimum of 10Gbps bandwidth at each interconnection point;
• Maintain a network consisting of fully redundant N x 100G links with each peering point;
• Establish interconnection with RETN in 3 separate mutually beneficial locations which are geographically separated by at least 2000km from each other;
• Be able to react quickly to establish additional capacity to meet traffic growth, and agree to upgrade connections at 70% utilisation;
• 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 upstreams;
• Not announce “martian” routes or the default route ( 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.

Main IPv4 / IPv6 exchange points

Internet Exchange Point




AMS-IX, Amsterdam 2001:7f8:1::a500:9002:1
B-CIX, Berlin 2001:7f8:19:1::232a:1
BIX, Budapest 2001:7f8:35::9002:1
BNIX, Brussels 2001:7f8:26::a500:9002:1
DE-CIX, Frankfurt 2001:7f8::232a:0:1
Espanix, Madrid 2001:7f8:f::68/64


France-IX, Paris 2001:7f8:54::17
INEX, Dublin LAN1 2001:7f8:18::117
INEX, Dublin LAN2 2001:7f8:18:12::81
LINX, London 2001:7f8:4::232a:1
MIX-IT, Milano 2001:7f8:b:100:1d1:a5d0:9002:116
Netnod, Stockholm



SwissIX, Zurich 2001:7f8:24::8f
VIX, Vienna 2001:7f8:30:0:2:1:0:9002


Equinix, Ashburn 2001:504:0:2::9002:1
NYIIX, New York 2001:504:1::a500:9002:1


BBIX, Tokyo 2001:de8:c::9002:1
BBIX, HongKong 2403:c780:b800:bb00::9002:1
Equinix, Singapore  2001:de8:4::9002:1
HKIX, Hong Kong 2001:7fa:0:1::ca28:a123
JPIX, Tokyo 2001:de8:8::9002:1
JPNAP, Tokyo 2001:7fa:7:1::9002:1
SGIX, Singapore 2001:de8:12:100::152


If you wish to peer with AS9002, send us your request to or via online Peering Contact Form (see below).

Please, provide your network description and technical details including:

– 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

Peering Contact Form

Back to top