ixreport

Paratus Africa: PeeringDB fix list

AS33763 · peeringdb.com/net/399

PeeringDB

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

Make the changes on Paratus 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 (4)

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. Angola Angola IXP Luanda, Angola · PeeringDB 421
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10G + 1G
    • In the entry with IPv4 196.223.1.28: set Speed to 1000 (1G) (now 10000).
  2. DR Congo KINIX Kinshasa, DR Congo · PeeringDB 628
    ProblemPeeringDB hasThe export has
    Port speed differs20G10G
    • In the entry with IPv4 196.223.28.38: set Speed to 10000 (10G) (now 20000).
  3. South Africa NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    Port speed differs100G2 × 100G

    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.

  4. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs100G2 × 100G

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