ixreport

MUBVUMELA: PeeringDB fix list

AS328916 · peeringdb.com/net/29874

PeeringDB

2 things to fix in MUBVUMELA's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on MUBVUMELA'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 (1)

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

  1. South Africa NAPAfrica IX Durban Durban, South Africa · PeeringDB 969From its IX-F export
    IPv4196.10.141.100
    IPv62001:43f8:6d2::100
    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.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs10G30G
    • In the entry with IPv4 196.60.10.226: set Speed to 30000 (30G) (now 10000).

    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/328916/: 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.