MTN South Africa: PeeringDB fix list

AS16637 · peeringdb.com/net/857

PeeringDB

2 things to fix in MTN South Africa's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.

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

Correct these entries (2)

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. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs500G500G + 10G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. South Africa NAPAfrica IX Durban Durban, South Africa · PeeringDB 969
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDB2001:43f8:6d2::1622001:43f8:6d2::62 2001:43f8:6d2::162
    Port speed differs20G2 × 20G
    • Add an entry: IPv4 –, IPv6 2001:43f8:6d2::62, speed 20000 (20G), RS peer yes.

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

From ixreport.com/net/16637/: 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.