ixreport

GENESIS TECHNOLOGY COMMUNICATION

AS30032 · Genesis Wireless

GENESIS TECHNOLOGY COMMUNICATION, LLC

5Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
5Using the route servers
2To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with GENESIS TECHNOLOGY COMMUNICATION? · Where should GENESIS TECHNOLOGY COMMUNICATION peer next? · Compare GENESIS TECHNOLOGY COMMUNICATION with another network

PeeringDB fix list Printable page · CSV

2 things to fix in GENESIS TECHNOLOGY COMMUNICATION's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 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.

Exchanges over time

0246Oct 3, 2026Nov 19, 20265
Show as a table
DateExchanges
Nov 19, 20265
Nov 18, 20265
Nov 17, 20265
Nov 16, 20265
Nov 15, 20265
Nov 14, 20265
Nov 13, 20265
Nov 12, 20265
Nov 11, 20265
Nov 10, 20265
Nov 9, 20265
Nov 8, 20265
Nov 7, 20265
Nov 6, 20265
Nov 5, 20265
Nov 4, 20265
Nov 3, 20265
Nov 2, 20265
Nov 1, 20265
Oct 31, 20265
Oct 30, 20265
Oct 29, 20265
Oct 28, 20265
Oct 27, 20265
Oct 26, 20265
Oct 25, 20265
Oct 24, 20265
Oct 23, 20265
Oct 22, 20265
Oct 21, 20265
Oct 20, 20265
Oct 19, 20265
Oct 18, 20265
Oct 17, 20265
Oct 16, 20265
Oct 15, 20265
Oct 14, 20265
Oct 13, 20265
Oct 12, 20265
Oct 11, 20265
Oct 10, 20265
Oct 9, 20265
Oct 8, 20265
Oct 7, 20265
Oct 6, 20265
Oct 5, 20265
Oct 4, 20265
Oct 3, 20265

Map

Where GENESIS TECHNOLOGY COMMUNICATION's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 50G across 5 exchanges.

United States FCIX Fremont, United States 206.80.238.119 10G Yes Both
United States IX-Denver Denver, United States 206.53.175.201 10G Yes Both
United States KCIX Kansas City, United States 206.51.7.67 10G Yes Both IPv6 not in PeeringDBSpeed differs
United States MICE Minneapolis, MN, United States 206.108.255.103 10G Yes Both
United States QCIX Davenport, United States 206.83.43.34 10G Yes Both IPv6 not in PeeringDB

Exchanges in its buildings that it isn't on (2)

These exchanges have a switch in a facility where GENESIS TECHNOLOGY COMMUNICATION lists itself in PeeringDB, but don't have GENESIS TECHNOLOGY COMMUNICATION as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

United States SIX SeattleSeattle, United States 372 Cologix MIN1
United States SIX Seattle (Jumbo)Seattle, United States 69 Cologix MIN1
Facilities (1)

The buildings GENESIS TECHNOLOGY COMMUNICATION lists in PeeringDB, and how many of the exchanges in each it's on.

United States Cologix MIN1Minneapolis 4 of 6