Peering Policy

Air Link has a selective peering policy, subject to the few basic technical, commercial, and legal requirements expressed in our peering policy, and to any local infrastructure requirements or constraints.

We offer peering on two different autonomous systems (AS numbers):

  • 393434 – Our US ASN
  • 264811 – Our TT ASN

We are able to peer at the Internet Exchanges (IXPs) and private facilities listed in our PeeringDB entry. Please choose the ASN physically closest to your location.

Peering Policy:

Air Link is listed in PeeringDB, the industry database for peering information for network operators. Please review our PeeringDB entry for the most current list of Air Link’s public and private peering locations. New peering requests should be submitted by sending a request to noc@airlinkdc.com.

Air Link has an open peering policy, subject to certain technical, commercial and legal requirements. At times, local infrastructure requirements or constraints may modify these requirements on a temporary or long-term basis.

Technical requirements:

Networks wishing to BGP peer with Air Link must have the following:

  • Publicly routable ASN.
  • Publicly routable address space (at least one /24 of IPv4 and/or one /48 of IPv6 space).
  • 24×7 NOC contact capable of resolving BGP routing issues.

Private peering physical requirements:

  • Standard port types: 1/10/25/40G Duplex Ethernet LR (LAN-PHY).
  • Link aggregation via LACP, preferred even for single links.
  • Optical physical layer: Single Mode Optical Fiber.
  • Direct point-to-point links only, only one device on each side, no support for switches in path to multiple routers or MLAG.
  • Only /30 IPv4 subnet sizes supported.

BGP configuration requirements:

  • No support for multihop.
  • Prefer MD5 authentication.
  • Most specific prefix accepted /24 (IPv4), /48 (IPv6).
  • We suggest peers set a max-prefix of 15,000 (IPv4) and 1,000 (IPv6) routes on peering sessions with Air Link.
  • Transit is not permitted unless prior agreement is agreed upon, in writing by all parties involved.
  • Neither party shall establish a static route, a route of last resort, or otherwise send traffic to the other party for a route not announced via BGP unless prior agreement is agreed upon, in writing by all parties involved.

Traffic requirements:

  • For traffic exchange, Air Link will generally prefer private peering links over public peering links, and public peering links over route-server paths.
  • Public:
      • Air Link generally does not have a minimum traffic requirement for public peering.
      • Although Air Link connects to Internet Exchange route servers where present, Air Link prefers to establish direct BGP sessions for traffic exchange.
  • Private:
    • For networks with sufficient traffic (generally above 1Gb/s), Air Link prefers private peering to better ensure quality of service.

Routing policy:

  • In general, peering sessions with AS393434 and AS264811 will advertise all AS-AIR-LINK routes. Depending on the intended usage this may be restricted.
  • We will be applying route filters to all our BGP sessions. To build these filters we will use your ASN data on the IRR system. To avoid any routing issues please keep your Maintainer, ASN, AS-SET, and Route/Route6 objects up to date.

Related ASNs:

Alongside AS393434 and AS364811, Air Link Networks also manages the following ASNs: AS61478

Disclaimers:

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(s) 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.