ixreport

Vodacom Congo: PeeringDB fix list

AS37453 · peeringdb.com/net/12051

PeeringDB

One thing to fix in Vodacom Congo's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Vodacom Congo'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. DR Congo KINIX Kinshasa, DR Congo · PeeringDB 628
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:3c0::29 2001:43f8:3c0::2a
    Port speed differs2 × 10G2 × 100G
    • In the entry with IPv4 196.223.28.41: set IPv6 to 2001:43f8:3c0::29 (now empty); set Speed to 100000 (100G) (now 10000).
    • In the entry with IPv4 196.223.28.42: set IPv6 to 2001:43f8:3c0::2a (now empty); set Speed to 100000 (100G) (now 10000).

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