HLkomm: PeeringDB fix list

AS16097 · peeringdb.com/net/1565

PeeringDB

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

Make the changes on HLkomm's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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 BCIX Berlin, Germany · PeeringDB 87
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 30G
    • In the entry with IPv4 193.178.185.241: set Speed to 30000 (30G) (now 100000).
    • In the entry with IPv4 193.178.185.41: set Speed to 30000 (30G) (now 100000).

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

  2. Germany DE-CIX Leipzig Leipzig, Germany · PeeringDB 4004
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 185.1.245.5: set Speed to 20000 (20G) (now 10000).
  3. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs100G12.5G
    • In the entry with IPv4 185.0.21.25: set Speed to 12500 (12.5G) (now 100000).

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