ixreport

Securebit AG: PeeringDB fix list

AS58057 · peeringdb.com/net/18724

PeeringDB

7 things to fix in Securebit AG's PeeringDB record, from what its exchanges publish: 1 to add, 6 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Securebit AG'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 (1)

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

  1. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64From its IX-F export and website members list
    IPv4193.239.118.8
    IPv62001:7f8:13::a505:8057:1
    SpeedNot published
    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 (6)

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 in PeeringDB, not in the export185.1.170.175 185.1.170.176185.1.170.175
    IPv6 address in PeeringDB, not in the export2001:7f8:9e::e2c9:0:1 2001:7f8:9e::e2c9:0:22001:7f8:9e::e2c9:0:1
    Port speed differs2 × 1G10G
    • In the entry with IPv4 185.1.170.175: set Speed to 10000 (10G) (now 1000).
    • The entry with IPv4 185.1.170.176, IPv6 2001:7f8:9e::e2c9:0:2 isn't in the export: delete it if that connection is gone.
  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 80.81.195.219: set Speed to 10000 (10G) (now 1000).
  3. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export185.1.210.185 185.1.210.223185.1.210.223
    IPv6 address in PeeringDB, not in the export2001:7f8:3d::e2c9:0:1 2001:7f8:3d::e2c9:0:22001:7f8:3d::e2c9:0:2
    Port speed differs2 × 1G10G
    • The entry with IPv4 185.1.210.185, IPv6 2001:7f8:3d::e2c9:0:1 isn't in the export: delete it if that connection is gone.
    • In the entry with IPv4 185.1.210.223: set Speed to 10000 (10G) (now 1000).
  4. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export185.1.208.180 185.1.208.191185.1.208.180
    IPv6 address in PeeringDB, not in the export2001:7f8:44::e2c9:0:1 2001:7f8:44::e2c9:0:22001:7f8:44::e2c9:0:2
    Port speed differs2 × 1G10G
    • In the entry with IPv4 185.1.208.180: set Speed to 10000 (10G) (now 1000).
    • The entry with IPv4 185.1.208.191, IPv6 2001:7f8:44::e2c9:0:1 isn't in the export: delete it if that connection is gone.
  5. United States EVIX Fremont, United States · PeeringDB 2274
    ProblemPeeringDB hasThe export has
    Port speed differs2G + 1G2 × 1G
    • In the entry with IPv4 206.81.104.242: set Speed to 1000 (1G) (now 2000).

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

  6. Germany KleyReX Frankfurt, Germany · PeeringDB 123
    ProblemPeeringDB hasThe export has
    Port speed differs1G100M
    • In the entry with IPv4 193.189.82.71: set Speed to 100 (100M) (now 1000).

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