Abtec Network Systems Peering Policy

Abtec Network Systems Ltd (Abtec) maintains a selective peering policy designed to deliver the best possible experience for customers. It is backed by industry standards and best practices, scaling for future demand and strategic placement of peering. Abtec reserves the right to make exceptions to the policy as deemed necessary. Abtec’s general requirements from your network are explained in the details below.

Technical requirements:
  • A fully redundant network with sufficient capacity to exchange traffic without congestion.
  • Peer will have a publicly routable Autonomous System Number (ASN)
  • Only IPv4 is supported
  • MD5 is supported
  • ASN details:
    • Abtec manages AS199286 with the organisation name ORG-ANSL4-RIPE
  • Routing policy:
    • Peer will have at least one publicly routable prefix less than or equal to /24
    • Abtec prefers to receive BGP community-tags from peers to indicate route origination
    • Unless specifically agreed upon beforehand, peers are expected to announce consistent routes in all locations where they peer with Abtec
    • In general, peering sessions with AS199286 will advertise all ANS-AS routes. Abtec may announce some regional specifics.
    • Neither party will establish a static route, a route of last resort, or otherwise send traffic to the other party for a route not announced via BGP
    • Peers are required to register their routes in a public Internet Routing Registry (IRR) database, for the purpose of filtering, and will keep this information up to date
    • Peers will adhere to MANRS industry standards for route security. At its sole discretion, Abtec may choose: 1.) not to establish peering with companies that do not have routes signed and registered; 2.) to remove invalid RPKI routes; 3.) not to accept routes from established peers that are not registered and signed
Operational requirements
  • A fully staffed 24×7 Network Operations Centre (NOC), capable of assisting in the resolution of all technical and performance issues, security violations, denial of service attacks, or any other abuse originating within the peer or their customers
  • Peers are expected to have a complete and up-to-date profile on PeeringDB including a 24×7 NOC email from corporate domain and phone number. We use this information to validate the peer’s details such as NOC information, technical contact information, and their presence at the peering facilities etc. Personal Yahoo, Gmail, and hotmail accounts are not accepted
Physical connection requirements
  • The locations where you can connect with Abtec for peering are listed in PeeringDB
  • Exchange peering:
    • Peers are expected to have at minimum a 1 Gb connection to the exchange
    • Peers are expected to upgrade their ports when peak utilisation exceeds 80%
    • Abtec encourages peers to maintain diverse connectivity to exchange to support fail-over scenarios