GorillaServers: PeeringDB fix list
AS53850 · peeringdb.com/net/14175
3 things to fix in GorillaServers's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on GorillaServers's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (2)
On the exchange's own member list, but not in GorillaServers's PeeringDB record. Add one entry per connection with these values.
-
IPv4 206.53.202.175 IPv6 2001:504:61::d25a:0:1 Speed 100000 Mbps (100G) RS peer Yes -
DE-CIX New York New York, United States · PeeringDB 804From its IX-F export and website members listIPv4 206.82.104.75 IPv6 2001:504:36::d25a:0:1 Speed 100000 Mbps (100G) RS peer Yes
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 Address belongs to another network in PeeringDB 206.82.104.75 is AS61438 ip-it consult GmbH 206.82.104.75 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
From ixreport.com/net/53850/: 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.