Prozeta: PeeringDB fix list

AS49025 · peeringdb.com/net/4580

PeeringDB

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

Make the changes on Prozeta'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 differs185.0.20.10 185.0.20.11 185.0.21.10185.0.21.49 185.0.21.50
    IPv6 address differs2001:7f8:7f::10 2001:7f8:7f::11 2001:7f8:7f::c:102001:7f8:7f::c:49 2001:7f8:7f::c:50
    • The entry with IPv4 185.0.20.10, IPv6 2001:7f8:7f::10 isn't in the export: delete it if that connection is gone.
    • The entry with IPv4 185.0.20.11, IPv6 2001:7f8:7f::11 isn't in the export: delete it if that connection is gone.
    • The entry with IPv4 185.0.21.10, IPv6 2001:7f8:7f::c:10 isn't in the export: delete it if that connection is gone.
    • Add an entry: IPv4 185.0.21.49, IPv6 2001:7f8:7f::c:49, speed 25000 (25G), RS peer yes.
    • Add an entry: IPv4 185.0.21.50, IPv6 2001:7f8:7f::c:50, speed 25000 (25G), RS peer yes.

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