ixreport

BAHAMUT-ZONE: PeeringDB fix list

AS204994 · peeringdb.com/net/15369

PeeringDB

8 things to fix in BAHAMUT-ZONE's PeeringDB record, from what its exchanges publish: 5 to add, 3 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on BAHAMUT-ZONE'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 (5)

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

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:d0::3:20c2:1
    SpeedNot published
    RS peerYes
  2. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214From its IX-F export and website members list
    IPv4185.1.170.145
    IPv62001:7f8:9e:0:3:20c2:0:1
    Speed10000 Mbps (10G)
    RS peerYes
  3. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74From its IX-F export and website members list
    IPv4185.1.210.149
    IPv62001:7f8:3d:0:3:20c2:0:1
    Speed10000 Mbps (10G)
    RS peerYes
  4. Germany DE-CIX Munich Munich, Germany · PeeringDB 248From its IX-F export and website members list
    IPv4185.1.208.146
    IPv62001:7f8:44:0:3:20c2:0:1
    Speed10000 Mbps (10G)
    RS peerYes
  5. Germany KleyReX Frankfurt, Germany · PeeringDB 123From its IX-F export and website members list
    IPv4193.189.82.70
    IPv62001:7f8:33::a120:4994: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.

Correct these entries (3)

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
    Address belongs to another network in PeeringDB185.1.170.145 is AS7768 Teknet Veri Merkezi185.1.170.145
    Address belongs to another network in PeeringDB2001:7f8:9e:0:3:20c2:0:1 is AS7768 Teknet Veri Merkezi2001:7f8:9e:0:3:20c2:0:1

    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.

  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB185.1.210.149 is AS7768 Teknet Veri Merkezi185.1.210.149
    Address belongs to another network in PeeringDB2001:7f8:3d:0:3:20c2:0:1 is AS7768 Teknet Veri Merkezi2001:7f8:3d:0:3:20c2:0:1

    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.

  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB185.1.208.146 is AS7768 Teknet Veri Merkezi185.1.208.146
    Address belongs to another network in PeeringDB2001:7f8:44:0:3:20c2:0:1 is AS7768 Teknet Veri Merkezi2001:7f8:44:0:3:20c2:0:1

    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/204994/: 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.