Vocus Peering Policy

What is Vocus' peering policy?

Vocus is an Australian based provider of network services to wholesale and corporate customers across the Asia-Pacific region, as well as our wholly owned retail subsidiaries in Australia and New Zealand.

We have a selective peering policy to ensure that peering is of mutual benefit to both parties.

Interconnection Requirements

Geographic Scope

The Requester must meet Vocus at a minimum of 4 mutually agreed, geographically diverse points across Australia. The interconnection points must include at least Sydney, Melbourne, Brisbane and Perth. Diverse interconnects are required within Sydney and Melbourne.

Infrastructure Requirements

The Requester shall maintain a fully redundant backbone network, and interconnect in Melbourne and Sydney at minimum port speed of 100GB. 10GB links are permitted in other states.

The requester should interconnect using both Internet Protocol version 4 (IPv4) and version 6 (IPv6) on each interface in parallel (dual stack). BGP protocol should be used to exchange routes.

Traffic Exchange Volume

The aggregate volume of traffic exchanged in each direction over all interconnect links between the Requester and Vocus shall equal or exceed 25% of total interconnect capacity, as measured on a 95th Percentile (95P) basis over a 21-day period.

Traffic Exchange Balance

The ratio of the aggregate amount of traffic exchanged between the Requester and Vocus shall be roughly balanced and shall not exceed 1.75:1 in a 31 day period. Traffic volumes for this calculations should be aggregated across all interconnects between both parties.

Operational Requirements

Each Network shall operate a fully staffed Network Operations Center (NOC) that is available 24 hours a day, 7 days a week and 365 days a year regardless of holidays or other special events.

Each Network must operate a fully redundant network, capable of handling a simultaneous single-node outage in each network without significantly affecting the performance of the traffic being exchanged.

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. The requester shall not announce the routes learnt from Vocus to other peering partners on their network or a transit provider. Such offenses shall be seen as a major violation of the policy, subject to the termination of the agreement.

The Requester must maintain a PeeringDB record containing up-to-date contacts and technical specifications.

The Requester must maintain an Internet Routing Registry AS-MACRO, providing accurate information on the prefixes which may be announced.

Vocus will not enter into a settlement-free peering relationship with current IP transit customers (or their downstream customers), or organizations that have purchased IP transit services from Vocus or it's subsidiaries in the past 12 months.

The peering policy is only a guideline. Meeting or exceeding all of the above requirements does not guarantee Vocus will enter into a peering relationship with Interconnection Candidate. Existing peering arrangement will have their status reviewed periodically to ensure capacity is sufficient for growth, contacts are refreshed for operations purposes, and all criteria continue to be met.

Disclaimer

Meeting the general qualifications is not a guarantee that a peering relationship with Vocus will be established. Vocus will evaluate several business factors and reserves the right not to enter into a peering agreement with an otherwise qualified applicant, and additionally reserves the right to waive any of the qualifications set forth above.

Vocus reserves the right to terminate peering, with established peers who do not meet the criteria described above.

Periodic review of the policies contained here will be conducted to ensure that the criteria and eligibility requirements are consistent with Vocus' business needs. Vocus may modify this peering policy at any time.

Last Updated 6th October 2026