CAPITEC BANK: PeeringDB fix list

AS327988 · peeringdb.com/net/21233

PeeringDB

2 things to fix in CAPITEC BANK's PeeringDB record, from what its exchanges publish: 1 to correct, 1 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.

Make the changes on CAPITEC BANK'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 (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 Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 20G2 × 20G + 2 × 10G

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

Exchanges that look shut down (1)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. South Africa NAPAfrica MAPS Cape Townghost Cape Town, South Africa · PeeringDB 3884

    Only one outside network

    IPv4196.46.25.28
    IPv6–
    Speed10000 Mbps (10G)
    IPv4196.46.25.29
    IPv6–
    Speed10000 Mbps (10G)

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