ixreport

Attix5 Africa: PeeringDB fix list

AS328536 · peeringdb.com/net/20854

PeeringDB

2 things to fix in Attix5 Africa's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Attix5 Africa'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 Attix5 Africa's PeeringDB record. Add one entry per connection with these values.

  1. South Africa NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597From its IX-F export
    IPv4196.60.71.131
    IPv62001:43f8:6d1::71:131
    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
    IPv6 address missing from PeeringDBnone2001:43f8:6d0::9:19
    • In the entry with IPv4 196.60.9.19: set IPv6 to 2001:43f8:6d0::9:19 (now empty).

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