Peering Policy – AS328677

Overview

AS328677 is an openly peering network. We welcome public and private peering with networks that offer a mutually beneficial traffic exchange. Our focus is on performance, resilience, and collaboration.

Policy Type

We operate an open peering policy with a mutually beneficial requirement. Peering requests are assessed on a case-by-case basis.

Peering Requirements

• Peers must operate a publicly routable Autonomous System (AS).
• Peers must have an up-to-date PeeringDB entry.
• Peers must maintain a 24/7 NOC contact reachable by email or phone.
• BGP sessions must be maintained with reasonable uptime (99.5%+ preferred).
• Both IPv4 and IPv6 peering are encouraged, but not mandatory.
• Peers must not engage in route leaks, path prepending abuse, or default route advertisement.
• IRR and RPKI filtering is enforced — invalid or unregistered prefixes will be dropped.
• Max-prefix limits must be respected. Excessive updates or flaps may lead to session dampening or deactivation.
• We expect traffic to be balanced or mutually valuable to both parties.

Routing Policy

• We use AS-SET: AFRINIC::AS-KORCOM for IRR filtering.
• We filter all BGP sessions using IRR and RPKI data.
• We announce only prefixes registered to AS328677.
• No transit or third-party prefixes will be advertised.
• No default routes will be accepted or advertised.
• We honor MED and BGP communities as documented in our PeeringDB.

Public Peering Locations

We are currently present at the following Internet Exchange Points (IXPs):

• Teraco JHB – [Isando (JHB) - South Africa]
• [More to be added as network expands]

Private Peering

Private peering is available in select facilities on a case-by-case basis. Please contact us to discuss options if you have significant traffic volume or strategic alignment.

Contact

• Peering Requests: [email protected]
• NOC: [email protected]
• PeeringDB: AS328677
• AS-SET:AS-KORCOM