General information

HE.NET RIPE PeeringDB

Peering policy

AS60438 practices an open peering policy which means that we peer with everyone who wants to peer with us. While we do not require any kind of written contract, you must follow these rules:

• Peers may only send traffic from their own and downstream networks to us.
• Peers must operate a Network Operations Center (NOC) reachable by email.
• Peers must keep their IRR and registry data up to date at any time.
• Peers shall enforce a strict routing policy to avoid route leaks.
• Peers shall aggregate their routes to avoid routing table inflation.

Technical Information

Please note the following preferences and technical information before entering a peering with us:

• Prefixes shorter than a /24 (IPv4) or /48 (IPv6) will be filtered.
• Prefixes with private or other invalid ASNs in AS_PATH will be filtered.
• Prefixes pointing to well-known bogon addresses will be filtered.
• Prefixes with invalid NEXT_HOP attribute will be filtered.
• We strongly encourage MD5 authentication for additional security.
• We support usage of the GRACEFUL_SHUTDOWN community.
• We configure an individual prefix limit for all peering sessions.

Physical Points of Presence

IXP	IPv4 Address	IPv6 Address	Type
FREMIX	185.1.214.3	2001:7f8:116:ee::3	Physical
KCIX	206.51.7.151	2001:504:1b:1::151	Physical
LL-IX	5.101.92.249	2001:678:4fc::92:249	Physical
Lambda-IX	149.112.26.14	2a0f:607:1070::14	Physical
EVIX	206.81.104.201	2602:fed2:fff:ffff::201	Physical
SBIX FRE	149.202.236.73	2001:7f8:d9:5d::ec16:1	Physical
4b42	185.1.125.44	2001:7f8:d0::ec16:1	Physical

Communities