ixreport

Aperture Networks: PeeringDB fix list

AS202562 · peeringdb.com/net/13715

PeeringDB

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

Make the changes on Aperture Networks'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 (2)

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
    Port speed differs10G1G
    • In the entry with IPv4 206.51.7.44: set Speed to 1000 (1G) (now 10000).
  2. Germany KleyReX Frankfurt, Germany · PeeringDB 123
    ProblemPeeringDB hasThe export has
    Port speed differs1G100M
    • In the entry with IPv4 193.189.82.219: set Speed to 100 (100M) (now 1000).

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