Eskom Holdings: PeeringDB fix list

AS37121 · peeringdb.com/net/27308

PeeringDB

2 things to fix in Eskom Holdings's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 20:58 UTC.

Make the changes on Eskom Holdings's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (2)

On the exchange's own member list, but not in Eskom Holdings's PeeringDB record. Add one entry per connection with these values.

  1. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4196.60.8.85
    IPv62001:43f8:6d0::85
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4196.60.9.85
    IPv62001:43f8:6d0::9:85
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. South Africa NAPAfrica MAPS Johannesburg Johannesburg, South Africa · PeeringDB 3403From its IX-F export

    2 connections, so 2 entries:

    IPv4196.46.25.150
    IPv6–
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4196.46.25.151
    IPv6–
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

From ixreport.com/net/37121/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.