Peering Policy

Netshelter operates under AS41047) and has an open peering policy. We will peer with networks that have a presence on mutual exchange points in accordance with the policies described below. In special cases we provide upstream announcement for other non-profit research networks and/or organisations.


To setup a connection, peering partners:

  • must have an up-to-date PeeringDB entry.
  • should have a well set-up route-set or AS-SET as well as up-to date prefix maximums defined in PeeringDB.
  • must have an up-to-date NOC contact email, which is responsive to raised issues and concerns.
  • must have an up-to-date Abuse contact email, which is responsive and acting on complaints and reports.

Peering requests can be send to and much include a small description of your network, ASN, AS-SET, Prefixes and preffered endpoint country/IXP.

Technical information

  • BGP communities for traffic engineering are available
  • MD5 Authentication is supported but not required
  • Prefixes shorter then /24 (IPv4) or /48 (IPv6) will be discarded
  • Bogon ASN will be discarded
  • Bogon prefixes will be discarded
  • RPKI invalid prefixes will be discarded
  • Prefix limit will be used for all peerings

Important notices

To ensure quality of operations, we reserve the following rights under our Peering Policy:

  • To alter our peering policy and peering requirements at any time.
  • To accept or decline a peering request at any time for any reason.
  • To suspend, without notice, peering connectivity in the event of a severe quality of service issue such as high latency, packet loss, or jitter pattern is detected and to take appropriate traffic engineering steps to maintain service quality.
  • To selectively withdraw prefixes from public IXP fabrics as needed to protect service quality.
  • To terminate any peering connection at any time without notice.

AS41047 details

The details on our network can be found at peeringDB: AS41047