ixreport

MikroTikSA Networks: PeeringDB fix list

AS328633 · peeringdb.com/net/22773

PeeringDB

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

Make the changes on MikroTikSA Networks'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. South Africa CINX Cape Town, South Africa · PeeringDB 344
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G + 1G

    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 Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G3 × 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.

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