Freenet Liberec: PeeringDB fix list

AS29504 · peeringdb.com/net/10537

PeeringDB

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

Make the changes on Freenet Liberec'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 differs91.213.211.185 185.0.20.184185.0.20.184 185.0.20.185
    IPv6 address in PeeringDB, not in the export2001:7f8:7f::184 2001:7f8:7f::185none
    • In the entry with IPv4 185.0.20.184: set IPv6 to (empty) (now 2001:7f8:7f::184).
    • The entry with IPv4 91.213.211.185, IPv6 2001:7f8:7f::185 isn't in the export: delete it if that connection is gone.
    • Add an entry: IPv4 185.0.20.185, IPv6 –, RS peer yes.

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