Gentlent GmbH: PeeringDB fix list
AS52112 · peeringdb.com/net/27298
3 things to fix in Gentlent GmbH's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check, 1 at exchanges that look shut down. As of 2026-10-08 18:53 UTC.
Make the changes on Gentlent GmbH'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 1G 200G - In the entry with IPv4 185.1.170.128: set Speed to 200000 (200G) (now 1000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Gentlent GmbH has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 119.11.187.112 IPv6 2404:c8:0:a:0:5:2112:1 Speed 1000 Mbps (1G)
Exchanges that look shut down (1)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only the operator's own networks
IPv4 194.153.158.3 IPv6 2001:7f8:89::3 Speed 10000 Mbps (10G)
From ixreport.com/net/52112/: 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.