Peering Policy

LNX Solutions (Pty) Ltd operates a multi-datacentre IP network across South Africa, delivering Internet transit, cloud, and mission-critical connectivity. To ensure the stability, efficiency, and resilience of our network, we maintain the following peering policy.

1. General Policy

LNX Solutions maintains a generally open peering policy. We welcome settlement-free peering with networks that can demonstrate operational competence, maintain adequate capacity, and share our commitment to reliable Internet routing.

We participate in public Internet Exchanges and may also establish bilateral private interconnections where appropriate.

2. Public Peering

LNX Solutions is present at the following Internet Exchange Points (IXPs):

• CINX (Cape Town Internet Exchange)
• JINX (Johannesburg Internet Exchange)
• NAPAfrica Cape Town (Teraco CT1)
• NAPAfrica Johannesburg (Teraco JB1)

We will generally peer openly with other participants at these IXPs, subject to compliance with this policy.

3. Private Peering

Private Network Interconnects (PNIs) may be established where traffic volumes justify the cost or where operational requirements (e.g., low latency, high bandwidth, or resilience) necessitate direct interconnection.

Requests for PNIs will be evaluated on a case-by-case basis.

4. Technical Requirements

Peers are expected to:

• Maintain a public ASN and up-to-date IRR / RPKI route objects.
• Announce only prefixes properly registered and allocated to their ASN.
• Maintain sufficient capacity to avoid sustained congestion (>70% utilization).
• Support BGP4 and standard routing practices (e.g., graceful session shutdown, MD5 if required).
• Implement prefix filtering and enforce basic routing hygiene (no spoofing, no default routes, no more specifics beyond /24 for IPv4 or /48 for IPv6 without agreement).
• Provide a 24x7 NOC contact for operational issues.

5. Operational Guidelines

• Each party is responsible for their own network, costs, and equipment at the interconnect.
• Either party may terminate a peering session with reasonable notice.
• Persistent routing leaks, hijacks, or abuse traffic may result in immediate suspension of the peering session.

6. Contact Information

Peering requests and operational queries may be directed to:

7. Exceptions

While LNX Solutions maintains a generally open peering policy, we reserve the right to decline or terminate peering requests that do not align with our technical, commercial, or security requirements.