Peering Policy

NHM applies an open peering policy to connect with any network with which we have a common presence at exchanges.

If peer is present at multiple exchanges, we do prefer to peer at every location.

The peering is based on good will and effort, therefore neither party is liable to the other party for losses or damage from interruption of peering for any period of time.

If a more formal/written agreement is needed on your side, feel free to contact us for an arrangement.

We put our effort to provide uncongested bandwidth at all the exchange points, monitoring constantly the bandwidth utilization with steady thresholded backhauling upgrades.

We have an Open Peering Policy but…

We peer direct where it makes sense:

• if your networks aren’t already on route servers;
• if we see your networks behind our transit;
• if there is some traffic to exchange or particular request;

We do not care so much about ratios and/or traffic volume that we need to carry to reach the peer.

We usually don’t peer with an existing customer’s peer.
This has political reasons as it may put existing peering relationships at risk.

If you peer with us you have to

• Establish your BGP session over IPv4 and IPv6;
• Only send us traffic destined to our prefixes;
• Do not point default route to us;
• Do not announce prefixes longer than /24 over IPv4 and /48 over IPv6;
• Have an up-to-date PeeringDB entry.

We apply the following rules to every peering session:

• We filter RFC1918 / RFC6598 / RFC5771 IPv4 addresses in either direction;
• We filter RFC4193 / RFC3307 IPv6 addresses in either direction;
• We filter BOGON addresses, both inbound and outbound
• We apply BCP38 filtering;
• We announce only networks with an AS_PATH starting with our own autonomous system as registered in the Ripe-NCC database;
• We accept only network with AS_PATH starting with peer’s own AS;
• We are matching RPKI validation state and we do reject invalids.

Peering Information

Contact Information

Everything related to our peering information maybe found at Peering DB website following this link:

https://www.peeringdb.com/asn/62275