ZET.NET: PeeringDB fix list

AS6204 · peeringdb.com/net/34203

PeeringDB

2 things to fix in ZET.NET's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on ZET.NET'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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 400G + 300G + 100G400G + 300G + 100G

    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 differs200G25G
    • In the entry with IPv4 185.0.20.31: set Speed to 25000 (25G) (now 200000).

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