This website uses cookies to improve your experience navigating our site. By continuing to browse, you are agreeing to our use of cookies. To learn more about how we use cookies, please view our Privacy Policy.


Information about AARNet's peering priorities, policies, locations and technical guidelines

We peer with many web content and service providers for the benefit of our customers

Peering is a commercial relationship between two Internet Service Providers (ISPs) 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 choose 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.

Who do we peer with?

We peer with a large number of web content and service providers in Australia such as Microsoft, YouTube, Amazon Web Services, Blackboard, Desire2Learn, and Netspot (Moodle), making content from these entities ‘on-net’ - which means high-performance and unlimited downloads for AARNet customers.

Peering Priorities

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.

Peering Policies

Our National and International Peering policies provide guidance to potential peers. These policies can be downloaded and viewed from the Resouces section at the bottom of this page.

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

Sites available via the peering fabric Sites available via private (Ethernet) cross connects

Los Angeles

  • One Wilshire (Any2)
  • Pacific Wave (via Seattle/Los Angeles VLAN)
  • Telehouse America (LAIIX/LAAP)

Adelaide, Pulteney Street Data Centre

Palo Alto, Switch and Data (PAIX)

  • NASA switch
  • PAIX switch

Canberra, TransACT

Perth, WAIX

Melbourne, Walsh St


  • Pacific Wave
  • Seattle Internet Exchange


  • Amnet IX
  • WAIX



  • Equinix
  • UTS Broadway


AARNet Autonomous System Number - 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

AARNet Peering IP Information

Site IPv4 IPv6 Notes

Los Angeles - Any2



Los Angeles - LAIIX/LAAP



Palo Alto - PAIX



Perth - WAIX 



Seattle - Pacific Wave



 (on VLAN 707)

(on VLAN 777)

Seattle - Seattle Internet Exchange 




More information and to request peering

Please contact our Network Operations Centre team


Guidelines for potential international peering partners:

AARNet International Peering Policy PDF (76KB)

Guidelines for potential national peering partners:

AARNet National Peering Policy PDF (68KB)