Australia’s research and education network

Log in
Fields marked with * are required

Peering

Peering is a commercial relationship between two Internet Service Providers (ISP) where they agree to provide access to (part of) each other's networks and services. If the two parties determine that the value/cost to each party of this service is similar then they may chose not to have any settlement between the parties (SKA peering).

Peering might take place over dedicated circuits or via a shared peering fabric (typically located at a neutral collocation facility or Internet exchange). The method chosen will depend on many factors,including the volume of traffic exchange, any special services required, etc.

Aims

AARNet is not interested in peering just for the sake of it but needs to see some value in the arrangement. This value might be improved performance by reducing latency between the parties or it might be the facilitation of advanced services, such as using multicast to deliver streaming content. Any peering must take into account the cost to AARNet, e.g. co-location costs, additional routers, interfaces,circuits, etc., and where the benefit is small AARNet may choose not to peer but continue using its transit relationships to source the traffic.

AARNet Policies

AARNet currently has two policies that provide guidance to potential peers.


It is envisioned that further policies will be developed to address the specific needs in each state and territory and these policies will restrict route exchange to only those routes available within the region (no national services will be made available for regional peering irrespective of the location of the national service).

AARNet favours using bi-lateral peering agreements as these provide AARNet with a direct relationship with the peer. AARNet would consider utilising an Internet Exchange to facilitate peering as long as bi-lateral peering is permitted and thus multi-lateral peering is not mandatory.

Peering Locations

The following sites are available for peering connections via the peering fabric:

  • Amsterdam, AMS-IX
  • Frankfurt, DE-CIX
  • London, LINX
  • Los Angeles
    • One Wilshire (Any2)
    • Pacific Wave (via Seattle/Los Angeles VLAN)
    • Telehouse America (LAIIX/LAAP)
  • Palo Alto, Switch and Data (PAIX)
    • NASA switch
    • PAIX switch
  • Perth, WAIX
  • Seattle
    • Pacific Wave
    • Seattle Internet Exchange

The following sites are available for peering via private (Ethernet based) cross connects:

  • Adelaide, Pulteney Street Data Centre
  • Canberra, TransACT
  • Melbourne, Walsh St
  • Perth
    • Amnet IX
    • WAIX
  • Sydney
    • Equinix
    • UTS Broadway

AARNET - AS7575

  • IPv4 prefixes defined by RADB macro AS7575:AS-CUSTOMERS. Approximately 270 prefixes announced.
  • IPv6 Prefixes 2001:388::/32. Currently announcing under 10 prefixes.
  • AARNet prefers to use MD5 authentication on BGP sessions. Our Peering DB entry is available from http://peeringdb.com/

Peering IP Information

Site IPv4 IPv6 Notes
Amsterdam - AMS-IX 195.69.145.243 2001:7f8:1::a500:7575:1
Frankfurt - DE-CIX 80.81.192.242 2001:7f8::1d97:0:1
London - LINX 195.66.224.206 2001:7f8:4::1d97:1
Los Angeles - Any2 206.223.143.64 2001:504:13::23
Los Angeles - LAIIX/LAAP 198.32.146.43 2001:504:A::A500:7575:1
Palo Alto - PAIX 198.32.176.177 2001:504:D::B1
Perth - WAIX 198.32.212.7 2001:7FA:11::1D97:0:1
Seattle - Pacific Wave

 207.231.242.2
198.32.171.32
 
 2001:504:B:11::2
2001:504:B:81::2
 
  (on VLAN 707)
 (on VLAN 777)
 
Seattle - Seattle Internet Exchange 198.32.180.112 2001:478:180::112

Contact Information

  • Peering requests to: peering<AT>aarnet.edu.au
  • Routing faults and issues to: noc<AT>aarnet.edu.au