ixreport

WANSEC: PeeringDB fix list

AS1421 · peeringdb.com/net/31007

PeeringDB

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

Make the changes on WANSEC'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. United States KCIX Kansas City, United States · PeeringDB 249
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB206.51.7.4206.51.7.4 206.51.7.222
    IPv6 address missing from PeeringDB2001:504:1b:1::42001:504:1b:1::4 2001:504:1b:1::222
    • Add an entry: IPv4 206.51.7.222, IPv6 2001:504:1b:1::222, speed 10000 (10G).

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