JON.CZ: PeeringDB fix list

AS196735 · peeringdb.com/net/14001

PeeringDB

One thing to fix in JON.CZ's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on JON.CZ'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 (1)

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 Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.0.20.130185.0.20.130 185.0.20.217
    IPv6 address missing from PeeringDB2001:7f8:7f::1302001:7f8:7f::130 2001:7f8:7f::217
    Port speed differs20G25G
    • In the entry with IPv4 185.0.20.130: set Speed to 25000 (25G) (now 20000).
    • Add an entry: IPv4 185.0.20.217, IPv6 2001:7f8:7f::217, speed 25000 (25G), RS peer yes.

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