ixreport

GVVME

AS12186

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

Tools: Where can I peer with GVVME? · Where should GVVME peer next? · Compare GVVME with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in GVVME's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on GVVME'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
    Port speed differs100G1G
    • In the entry with IPv4 206.51.7.70: set Speed to 1000 (1G) (now 100000).

Exchanges over time

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

Map

Where GVVME'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 120G across 3 exchanges.

United States HOUIX Houston, United States 206.83.136.76 2001:504:9e::76 10G Both
United States KCIX Kansas City, United States 206.51.7.70 2001:504:1b:1::70 100G Yes Both Speed differs
United States SIX Seattle Seattle, United States 206.81.81.156 2001:504:16::2f9a 10G Yes Both

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

These exchanges have a switch in a facility where GVVME lists itself in PeeringDB, but don't have GVVME 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 MICEMinneapolis, MN, United States 157 1530 SWIFT - NOCIX
United States STLIXSaint Louis, MO, United States 108 1530 SWIFT - NOCIX
United States IX-DenverDenver, United States 96 1530 SWIFT - NOCIX
United States SIX Seattle (Jumbo)Seattle, United States 69 1530 SWIFT - NOCIX
United States F4IX MCIKansas City, United States 67 1530 SWIFT - NOCIX
United States HN Internet Exchange (Main)North Kansas City, United States 27 1530 SWIFT - NOCIX
United States SpringIXSpringfield, MO, United States 22 1530 SWIFT - NOCIX
United States DesMoinesIXDes Moines, United States 11 1530 SWIFT - NOCIX
United States SIOUIXSioux City, United States 4 1530 SWIFT - NOCIX
United States MOCIXKansas City, United States 3 1530 SWIFT - NOCIX
Facilities (2)

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

United States 1530 SWIFT - NOCIXNorth Kansas City 3 of 13
United States NOCIX Clay FacilityNorth Kansas City 1 of 1