GVVME
AS12186
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.
-
Problem PeeringDB has The export has Port speed differs 100G 1G - In the entry with IPv4 206.51.7.70: set Speed to 1000 (1G) (now 100000).
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 3 |
| Nov 18, 2026 | 3 |
| Nov 17, 2026 | 3 |
| Nov 16, 2026 | 3 |
| Nov 15, 2026 | 3 |
| Nov 14, 2026 | 3 |
| Nov 13, 2026 | 3 |
| Nov 12, 2026 | 3 |
| Nov 11, 2026 | 3 |
| Nov 10, 2026 | 3 |
| Nov 9, 2026 | 3 |
| Nov 8, 2026 | 3 |
| Nov 7, 2026 | 3 |
| Nov 6, 2026 | 3 |
| Nov 5, 2026 | 3 |
| Nov 4, 2026 | 3 |
| Nov 3, 2026 | 3 |
| Nov 2, 2026 | 3 |
| Nov 1, 2026 | 3 |
| Oct 31, 2026 | 3 |
| Oct 30, 2026 | 3 |
| Oct 29, 2026 | 3 |
| Oct 28, 2026 | 3 |
| Oct 27, 2026 | 3 |
| Oct 26, 2026 | 3 |
| Oct 25, 2026 | 3 |
| Oct 24, 2026 | 3 |
| Oct 23, 2026 | 3 |
| Oct 22, 2026 | 3 |
| Oct 21, 2026 | 3 |
| Oct 20, 2026 | 3 |
| Oct 19, 2026 | 3 |
| Oct 18, 2026 | 3 |
| Oct 17, 2026 | 3 |
| Oct 16, 2026 | 3 |
| Oct 15, 2026 | 3 |
| Oct 14, 2026 | 3 |
| Oct 13, 2026 | 3 |
| Oct 12, 2026 | 3 |
| Oct 11, 2026 | 3 |
| Oct 10, 2026 | 3 |
| Oct 9, 2026 | 3 |
| Oct 8, 2026 | 3 |
| Oct 7, 2026 | 3 |
| Oct 6, 2026 | 3 |
| Oct 5, 2026 | 3 |
| Oct 4, 2026 | 3 |
| Oct 3, 2026 | 3 |
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.
| HOUIX Houston, United States | 10G | Both | |
| KCIX Kansas City, United States | 100G | Both Speed differs | |
| SIX Seattle Seattle, United States | 10G | Both |
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.
| MICEMinneapolis, MN, United States | 157 | |
| STLIXSaint Louis, MO, United States | 108 | |
| IX-DenverDenver, United States | 96 | |
| SIX Seattle (Jumbo)Seattle, United States | 69 | |
| F4IX MCIKansas City, United States | 67 | |
| HN Internet Exchange (Main)North Kansas City, United States | 27 | |
| SpringIXSpringfield, MO, United States | 22 | |
| DesMoinesIXDes Moines, United States | 11 | |
| SIOUIXSioux City, United States | 4 | |
| MOCIXKansas City, United States | 3 |
Facilities (2)
The buildings GVVME lists in PeeringDB, and how many of the exchanges in each it's on.
| 1530 SWIFT - NOCIXNorth Kansas City | 3 of 13 | |
| NOCIX Clay FacilityNorth Kansas City | 1 of 1 |