ixreport

GENESIS TECHNOLOGY COMMUNICATION: PeeringDB fix list

AS30032 · peeringdb.com/net/12528

PeeringDB

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

Make the changes on GENESIS TECHNOLOGY COMMUNICATION'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
    IPv6 address missing from PeeringDBnone2001:504:1b:1::67
    Port speed differs10G1G
    • In the entry with IPv4 206.51.7.67: set IPv6 to 2001:504:1b:1::67 (now empty); set Speed to 1000 (1G) (now 10000).
  2. United States QCIX Davenport, United States · PeeringDB 2741
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:504:9b::34
    • In the entry with IPv4 206.83.43.34: set IPv6 to 2001:504:9b::34 (now empty).

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