cyberways GmbH: PeeringDB fix list

AS13132 · peeringdb.com/net/1467

PeeringDB

4 things to fix in cyberways GmbH's PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on cyberways GmbH'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 (3)

On the exchange's own member list, but not in cyberways GmbH'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.46
    IPv62001:7f8:9e::334c:0:1
    Speed1000 Mbps (1G)
    RS peerYes
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74From its IX-F export and website members list
    IPv4185.1.210.65
    IPv62001:7f8:3d::334c:0:1
    Speed1000 Mbps (1G)
    RS peerYes
  3. Germany OpenCarrier OCIX Duesseldorf, Germany · PeeringDB 170From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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.

  1. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.208.82185.1.208.54 185.1.208.82
    IPv6 address missing from PeeringDB2001:7f8:44::334c:0:22001:7f8:44::334c:0:1 2001:7f8:44::334c:0:2
    Port speed differs1G2 × 1G
    • Add an entry: IPv4 185.1.208.54, IPv6 2001:7f8:44::334c:0:1, speed 1000 (1G), RS peer yes.

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