COVID-19 Update
Peering policy banner

WebReach / SAIX peering policy

Telkom SA SOC Limited t/a Openserve Peering Policy

Tag with star icon

The following sets out the policy in terms of which Telkom SA SOC Limited t/a Openserve ("Openserve") will evaluate requests made by parties ("peering applicants") seeking to exchange internet protocol ("IP") traffic with Openserve on a settlement-free or shared-cost basis within the borders of South Africa.

This policy applies to all requests for settlement-free or shared cost peering with Openserve, either via dedicated peering connections ("private peering") or via an internet exchange peering point ("public peering"). Notwithstanding the aforesaid, the decision to peer with any other entity is in Openserve's sole discretion and nothing within this policy is to be construed as creating the impression that Openserve will be obliged or prepared to peer with any applicant for peering, regardless of whether or not such applicant meets Openserve's criteria for peering in terms of this Peering Policy.

Openserve's Internet presence is represented by the Autonomous System ("AS") number 5713 and this Peering Policy applies to all requests for peering with AS5713.

Info icon

NOTE: This policy replaces all previous Telkom wholesale or Openserve peering policies. This policy is effective as of 1st July 2016.

Peering policy criteria

List icon
General guidelines
  • In order to be eligible for peering, a peering applicant must demonstrate that it is able to satisfy the criteria contained within this peering policy on an ongoing basis.
  • Openserve AS5713 will not peer with clients of existing peers.
  • Other than where Openserve elects, at its sole discretion, to peer with certain entities for the purpose of connecting Openserve clients to such entities' content (e.g. Google, Microsoft, Netflix etc), Openserve AS5713 will not peer with entities which do not possess an ECNS or ECS license.
  • An autonomous system number ("ASN") that is a client of Openserve AS5713 for any internet services may not simultaneously peer with Openserve and will accordingly not be considered as an applicant for peering under this peering policy.
  • An MPLS VPN network will specifically not be considered for peering in this peering policy. Only Internet networks utilised for the provision of open domain internet services shall be contemplated in this peering policy.
  • Openserve will, at its sole discretion, peer either publicly or privately.
Suitcase icon
Operational and backbone requirements
  • An applicant must have a fully serial or parallel redundant backbone network in South Africa, in which the majority of its inter-hub trunk links between Johannesburg/Pretoria, Durban and Cape Town, must be connected to the applicant's core network nodes.
  • The national network of an applicant must be capable of handling single-node outages in each geographic network region without significantly affecting the traffic being transited end-to-end over its network or traffic exchanged across the peering links established between Openserve and the peering partner.
  • An applicant must operate its network as a single AS with an associated single ASN for its domestic backbone network. If the applicant's internet network uses multiple ASNs then, at Openserve's discretion, both networks will exchange routes equivalent to the total internet network footprint in all of the regions where such peering applicant has an ASN.
  • An applicant must operate a Network Operations Centre (NOC) which is staffed 24 x 7 x 365.
  • An applicant must operate nation-wide internet network facilities that terminate Internet client leased lines onto a device on that network.
  • An applicant must have internet network core nodes in the following domestic locations with a geographically ubiquitous internet network in all the following regions: Johannesburg / Pretoria, Cape Town and Durban.
  • An applicant must have comparative domestic and international backbone capacities.
  • An applicant must be able to establish at least two peering points in South Africa, with at least one peering point in each of Johannesburg and Cape Town.
Road signs icon
Routing requirements and traffic ratios
  • Each party must set the next hop to be itself, the advertising router of the network. Each party will propagate such routes to its transit clients with its own router as next hop.
  • A peering partner must employ closest-exit routing for all internet traffic intended for peering.
  • Peering routes do not replace, or serve as a substitute for, internet transit services of a peering partner or Openserve AS 5713.
    • Local and long-distance domestic transit internet traffic of the peering partner must remain on the internet network of the peering partner.
    • The peering partner must give a written undertaking that no VPNs of or on its network make use of the peering between the peering partner and Telkom AS 5713. For the purpose of this Peering Policy, reference to VPNs excludes secure internet (https) sessions (such as internet banking).
    • The peering partner shall not be permitted to offer or sell any IP transit services providing only Telkom's AS 5713.
  • Routes must be registered with recognized route registries such as ARIN and AFRINIC. Only registered routes must be announced. These routes must belong to the peering partners and their clients.
  • The peering partner must announce all peering routes across peering links equally.
  • No route of last resort (default route) or static routing will be directed at Openserve AS 5713.
  • All routes exchanged must be the peering partner's and the peering partner's clients' routes. Routes from one peering partner are not announced to other peering partners (no transit). Routes from peering partners are not announced to upstream transit providers. Routes from upstream transit providers are not announced to peering partners.
  • Openserve AS 5713 shall not be obliged to convey a peering partner's traffic to a region where the peering partner concerned does not operate an internet network.
  • The combined capacity of the peering ports between a peering partner's internet network and Openserve AS 5713 must not exceed 75% of the said peering partner's core network capacity between Johannesburg and Cape Town.
  • The aggregate amount of traffic exchanged in each direction over all interconnection links between the peering applicant and Openserve shall be equal to or exceed 300 Mbps of traffic for either private or public peering.
  • The ratio of the aggregate amount of traffic exchanged between the peering applicant and Openserve shall be balanced and the ratio of inbound and outbound traffic shall not exceed a ratio of 1.8:1, as measured by Openserve on an ongoing basis.
Globe atlas icon
General policy notices
  • This peering policy is only a guideline and meeting or exceeding all of the criteria set forth in this policy does not guarantee that Openserve will enter into a peering relationship with a peering applicant.
  • Where deemed appropriate any consideration of a peering request will be subjected to a 3 month trial period before a final peering arrangement is made. During the trial the peering applicant may not terminate any existing IP transit services leased from Openserve or withhold payment of existing IP transit services.
  • Applicants for peering with Openserve will be required to enter into an Openserve nondisclosure agreement and successful applicants will be required to sign Openserve's Peering Agreement in order to commence peering with Openserve.
  • Should a peering partner fail to continue to meet the criteria contained in this peering policy at any stage for the duration of a peering arrangement, and fail to remedy the situation within 90 calendar days (or such longer period as may be agreed upon in writing between Openserve and the peering partner) of receipt of a notice to remedy the situation, Openserve shall be entitled to terminate the peering arrangement.
  • In addition to the above, Openserve will conduct periodic reviews of this peering policy to ensure that it remains consistent with changes in Openserve's AS 5713. This may result in this peering policy being amended or replaced at any time. Any peering arrangements in existence at the time that this amended peering policy is introduced will automatically be amended with the latest peering policy terms and conditions on receipt of a notice to this effect from Openserve. The peering partner shall, in writing within 90 days, accept the new peering policy, failing which Openserve shall be entitled to terminate the peering arrangement in place at the time.
  • The criteria set forth in this policy are not exhaustive and any final peering executed by Openserve and the peering applicant will contain additional terms and conditions.

All questions/enquiries about peering with Openserve can be sent to an Openserve Account Manager or