ixreport

KINIX Route Servers: PeeringDB fix list

AS37431 · peeringdb.com/net/10761

PeeringDB

One thing to fix in KINIX Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on KINIX Route Servers'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::1 2001:43f8:3c0::2
    Port speed differs2 × 10G200G + 10G + 1G
    • In the entry with IPv4 196.223.28.1: set IPv6 to 2001:43f8:3c0::1 (now empty); set Speed to 1000 (1G) (now 10000).
    • In the entry with IPv4 196.223.28.2: set IPv6 to 2001:43f8:3c0::2 (now empty).

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