ixreport

TKR Jasek: PeeringDB fix list

AS207187 · peeringdb.com/net/15594

PeeringDB

2 things to fix in TKR Jasek's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on TKR Jasek'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 (2)

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. Czechia NIX.CZ Prague, Czechia · PeeringDB 71
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 50G50G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 25G + 10G7.5G
    • In the entry with IPv4 185.0.20.158: set Speed to 7500 (7.5G) (now 25000).
    • In the entry with IPv4 185.0.20.99: set Speed to 7500 (7.5G) (now 10000).
    • In the entry with IPv4 185.0.21.12: set Speed to 7500 (7.5G) (now 25000).

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