GMCHOSTING
AS19186 · GMCHosting
GMCHOSTING LLC
Tools: Where can I peer with GMCHOSTING? · Where should GMCHOSTING peer next? · Compare GMCHOSTING with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
3 things to fix in GMCHOSTING's PeeringDB record, from what its exchanges publish: 1 to correct, 2 to check. As of 2026-11-19 12:40 UTC.
Make the changes on GMCHOSTING'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 IPv6 address in PeeringDB, not in the export 2001:504:16::4af2 none - In the entry with IPv4 206.81.81.227: set IPv6 to (empty) (now 2001:504:16::4af2).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (2)
In PeeringDB, but on none of the exchange's own lists. If GMCHOSTING has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
Any2East Washington DC, Reston, Boston, New York, Atlanta, United States · PeeringDB 204Not on its website members list
IPv4 206.51.40.126 IPv6 2001:504:13:1::126 Speed 10000 Mbps (10G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 195.66.227.199 IPv6 2001:7f8:4::4af2:1 Speed 10000 Mbps (10G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 4 |
| Nov 18, 2026 | 4 |
| Nov 17, 2026 | 4 |
| Nov 16, 2026 | 4 |
| Nov 15, 2026 | 4 |
| Nov 14, 2026 | 4 |
| Nov 13, 2026 | 4 |
| Nov 12, 2026 | 4 |
| Nov 11, 2026 | 4 |
| Nov 10, 2026 | 4 |
| Nov 9, 2026 | 4 |
| Nov 8, 2026 | 4 |
| Nov 7, 2026 | 4 |
| Nov 6, 2026 | 4 |
| Nov 5, 2026 | 4 |
| Nov 4, 2026 | 4 |
| Nov 3, 2026 | 4 |
| Nov 2, 2026 | 4 |
| Nov 1, 2026 | 4 |
| Oct 31, 2026 | 4 |
| Oct 30, 2026 | 4 |
| Oct 29, 2026 | 4 |
| Oct 28, 2026 | 4 |
| Oct 27, 2026 | 4 |
| Oct 26, 2026 | 4 |
| Oct 25, 2026 | 4 |
| Oct 24, 2026 | 4 |
| Oct 23, 2026 | 4 |
| Oct 22, 2026 | 4 |
| Oct 21, 2026 | 4 |
| Oct 20, 2026 | 4 |
| Oct 19, 2026 | 4 |
| Oct 18, 2026 | 4 |
| Oct 17, 2026 | 4 |
| Oct 16, 2026 | 4 |
| Oct 15, 2026 | 4 |
| Oct 14, 2026 | 4 |
| Oct 13, 2026 | 4 |
| Oct 12, 2026 | 4 |
| Oct 11, 2026 | 4 |
| Oct 10, 2026 | 4 |
| Oct 9, 2026 | 4 |
| Oct 8, 2026 | 4 |
| Oct 7, 2026 | 4 |
| Oct 6, 2026 | 4 |
| Oct 5, 2026 | 4 |
| Oct 4, 2026 | 4 |
| Oct 3, 2026 | 4 |
Map
Where GMCHOSTING'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.
| Any2East Washington DC, Reston, Boston, New York, Atlanta, United States | 10G | PeeringDB | |
| Equinix Dallas Dallas, United States | 10G | PeeringDB | |
| LINX LON1 London, United Kingdom | 10G | PeeringDB only | |
| SIX Seattle Seattle, United States | 10G | Both IPv6 not in export |
GMCHOSTING lists no facilities in PeeringDB.