ixreport

BAHAMUT-ZONE

AS204994

Luke Seabrook

5Exchanges
5On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
5Using the route servers
8To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with BAHAMUT-ZONE? · Where should BAHAMUT-ZONE peer next? · Compare BAHAMUT-ZONE with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

8 things to fix in BAHAMUT-ZONE's PeeringDB record, from what its exchanges publish: 5 to add, 3 to correct. As of 2026-11-19 18:41 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.

Exchanges over time

0246Oct 3, 2026Nov 19, 20265
Show as a table
DateExchanges
Nov 19, 20265
Nov 18, 20265
Nov 17, 20265
Nov 16, 20265
Nov 15, 20265
Nov 14, 20265
Nov 13, 20265
Nov 12, 20265
Nov 11, 20265
Nov 10, 20265
Nov 9, 20265
Nov 8, 20265
Nov 7, 20265
Nov 6, 20265
Nov 5, 20265
Nov 4, 20265
Nov 3, 20265
Nov 2, 20265
Nov 1, 20265
Oct 31, 20265
Oct 30, 20265
Oct 29, 20265
Oct 28, 20265
Oct 27, 20265
Oct 26, 20265
Oct 25, 20265
Oct 24, 20265
Oct 23, 20265
Oct 22, 20265
Oct 21, 20265
Oct 20, 20265
Oct 19, 20265
Oct 18, 20265
Oct 17, 20265
Oct 16, 20265
Oct 15, 20265
Oct 14, 20265
Oct 13, 20265
Oct 12, 20265
Oct 11, 20265
Oct 10, 20265
Oct 9, 20265
Oct 8, 20265
Oct 7, 20265
Oct 6, 20265
Oct 5, 20265
Oct 4, 20265
Oct 3, 20265

Map

Where BAHAMUT-ZONE's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 30.1G, at the 4 of 5 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::3:20c2:1 Yes Not in PeeringDB
Germany DE-CIX Dusseldorf Düsseldorf, Germany 185.1.170.145 2001:7f8:9e:0:3:20c2:0:1 10G Up, 0 routes Not in PeeringDB Address taken
Germany DE-CIX Hamburg Hamburg, Germany 185.1.210.149 2001:7f8:3d:0:3:20c2:0:1 10G Up, 0 routes Not in PeeringDB Address taken
Germany DE-CIX Munich Munich, Germany 185.1.208.146 2001:7f8:44:0:3:20c2:0:1 10G Up, 0 routes Not in PeeringDB Address taken
Germany KleyReX Frankfurt, Germany 193.189.82.70 2001:7f8:33::A120:4994:1 100M Yes Not in PeeringDB

BAHAMUT-ZONE lists no facilities in PeeringDB.