ixreport

Mzansi ComNet: PeeringDB fix list

AS328674 · peeringdb.com/net/27542

PeeringDB

3 things to fix in Mzansi ComNet's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-10-08 18:53 UTC.

Make the changes on Mzansi ComNet'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 (3)

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

  1. South Africa DINX Durban, South Africa · PeeringDB 610From its IX-F export
    IPv4196.223.30.193
    IPv62001:43f8:1f2::193
    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 JINX Johannesburg, South Africa · PeeringDB 129From its IX-F export
    IPv4196.60.96.193
    IPv62001:43f8:1f0::193
    Speed1000 Mbps (1G)
    RS peerYes

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

  3. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592From its IX-F export and website members list
    IPv4196.60.9.116
    IPv62001:43f8:6d0::9:116
    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/328674/: 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.