GMCHOSTING: PeeringDB fix list
AS19186 · peeringdb.com/net/18469
3 things to fix in GMCHOSTING's PeeringDB record, from what its exchanges publish: 1 to correct, 2 to check. As of 2026-10-08 18:53 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 listIPv4 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)
From ixreport.com/net/19186/: 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.