ixreport

ZlinNet: PeeringDB fix list

AS47114 · peeringdb.com/net/36343

PeeringDB

One thing to fix in ZlinNet's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on ZlinNet'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.146185.0.20.146 185.0.21.146
    IPv6 address missing from PeeringDB2001:7f8:7f::1462001:7f8:7f::146 2001:7f8:7f::c:146
    Port speed differs20G6.25G
    • In the entry with IPv4 185.0.20.146: set Speed to 6250 (6.25G) (now 20000).
    • Add an entry: IPv4 185.0.21.146, IPv6 2001:7f8:7f::c:146, speed 6250 (6.25G), RS peer yes.

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