AFR-IX Telecom: PeeringDB fix list

AS60171 · peeringdb.com/net/6572

PeeringDB

7 things to fix in AFR-IX Telecom's PeeringDB record, from what its exchanges publish: 2 to add, 5 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on AFR-IX Telecom'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 (2)

On the exchange's own member list, but not in AFR-IX Telecom's PeeringDB record. Add one entry per connection with these values.

  1. Cameroon Douala-IX Douala, Cameroon · PeeringDB 3561From its IX-F export
    IPv4196.60.84.84
    IPv62001:43fd:c000:d0ae::eb0b
    Speed1000 Mbps (1G)
    RS peerYes
  2. Rwanda RINEX Kigali, Rwanda · PeeringDB 1032From its IX-F export
    IPv4196.223.12.231
    IPv62001:43f8:150::231
    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 (5)

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. Spain CATNIX Barcelona, Spain · PeeringDB 62
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export193.242.98.147none
    IPv6 address in PeeringDB, not in the export2001:7f8:2a:0:2:1:6:171none
    Port speed differs100G20G
    • The entry with IPv4 193.242.98.147, IPv6 2001:7f8:2a:0:2:1:6:171 isn't in the export: delete it if that connection is gone.

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

  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G100G

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

  3. DR Congo KINIX Kinshasa, DR Congo · PeeringDB 628
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:3c0::23
    • In the entry with IPv4 196.223.28.35: set IPv6 to 2001:43f8:3c0::23 (now empty).
  4. Kenya KIXP - Nairobi Nairobi, Kenya · PeeringDB 236
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB196.223.21.143196.223.21.143 196.223.21.181
    IPv6 address missing from PeeringDB2001:43f8:60:1::1432001:43f8:60:1::143 2001:43f8:60:1::181
    Port speed differs10G2 × 10G
    • Add an entry: IPv4 196.223.21.181, IPv6 2001:43f8:60:1::181, speed 10000 (10G), RS peer no.
  5. South Africa NAPAfrica IX Durban Durban, South Africa · PeeringDB 969
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 196.10.141.69: set Speed to 100000 (100G) (now 10000).

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