ixreport

Boecker Elektronik: PeeringDB fix list

AS204625

4 things to fix in Boecker Elektronik's PeeringDB record, from what its exchanges publish: 4 to add. As of 2026-10-08 18:53 UTC.

AS204625 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (4)

On the exchange's own member list, but not in Boecker Elektronik's PeeringDB record. Add one entry per connection with these values.

  1. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214From its IX-F export and website members list
    IPv4185.1.170.61
    IPv62001:7f8:9e:0:3:1f51:0:1
    Speed10000 Mbps (10G)
    RS peerYes
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74From its IX-F export and website members list
    IPv4185.1.210.86
    IPv62001:7f8:3d:0:3:1f51:0:1
    Speed10000 Mbps (10G)
    RS peerYes
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248From its IX-F export and website members list
    IPv4185.1.208.80
    IPv62001:7f8:44:0:3:1f51:0:1
    Speed10000 Mbps (10G)
    RS peerYes
  4. Germany KleyReX Frankfurt, Germany · PeeringDB 123From its IX-F export and website members list
    IPv4193.189.82.191
    IPv62001:7f8:33::a120:4625:1
    Speed100 Mbps (100M)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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