GELSEN NET: PeeringDB fix list

AS16024 · peeringdb.com/net/13202

PeeringDB

4 things to fix in GELSEN NET's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on GELSEN NET'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 (4)

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.

  1. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    IPv4 address differs185.1.170.111 185.1.171.13185.1.170.98 185.1.171.13
    IPv6 address differs2001:7f8:9e::3e98:0:1 2001:7f8:9e::3e98:0:22001:7f8:9e::3e98:0:2 2001:7f8:9e::3e98:0:3
    Port speed differs2 × 10G100G + 10G
    • The entry with IPv4 185.1.170.111, IPv6 2001:7f8:9e::3e98:0:1 isn't in the export: delete it if that connection is gone.
    • Add an entry: IPv4 185.1.170.98, IPv6 2001:7f8:9e::3e98:0:3, speed 100000 (100G), RS peer yes.
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.210.122: set Speed to 100000 (100G) (now 10000).
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.208.120: set Speed to 100000 (100G) (now 10000).
  4. Germany Ruhr-CIX Ruhr Region, Germany · PeeringDB 3405
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 185.1.197.2: set Speed to 10000 (10G) (now 100000).

From ixreport.com/net/16024/: 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.