Peering Policy


ITsjefen AS have a community-first approach to interconnecting with other Internet connected parties and will therefore seek to peer with potential peers on a settlement-free basis when such interconnections are of mutual benefit to both parties.
Our AS 44381 is currently based in Trondheim, Norway.
For direct peering at our POPs we do not require formal contracts for peering arrangements, but the following guidelines always apply;
  • Meeting the requirements of this document does not require us to establish a peering relationship with any party.
  • Any network that is a BGP customer of ITsjefen or a partner network can not use its peering to transit access.
  • All peers must supply an operational contact that is available on a 24x7 basis such as a Network Operations Center or equivalent. Both voice and e-mail contact information is required.
  • Peers should, whenever possible, provide an accessible looking glass and/or traceroute server to assist the peering community in troubleshooting.
  • Peer must agree to actively cooperate to resolve security incidents and other operational problems.
  • A good faith effort should be made to communicate information regarding network maintenance that will affect traffic patterns.


    • Technical and Routing Requirements
  • Peers must not utilize any form of gateway of last resort or default route that is directed at the interconnect.
  • Neither party shall modify, sell or provide the next-hop to a third party.
  • All announcements are to be consistent, in terms of prefix aggregation properties, across all peering locations.
  • Peers are expected to filter their clients to reject both unauthorized BGP announcements, aggregate prefixes announced as well as filter their prefixes in a correct manner according to route objects.
  • Use of the Internet Routing Registry is encouraged.


    • Suspension and Termination
    For direct peering at our POPs and otherwise when not covered by a peering location contract, ITsjefen reserve the right to suspend peering for an indefinite period of time should any form of network abuse via the peering.
    Recurring incidents of network abuse and/or slow responses to an incident will result in termination of the peering relationship.
    ITsjefen AS reserves the right to terminate direct peering at our POPs or otherwise when not covered by a peering contract for any reason with 60 days notice.


    The definition of network abuse includes but is not limited to:
  • Denial of Service attacks
  • Unsolicited Bulk Email sources
  • Setting default-route to the peering


    • For peering requests - email: noc - a t - ITsjefen - d o t - no