gsnet.cz: PeeringDB fix list

AS47949 · peeringdb.com/net/15042

PeeringDB

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

Make the changes on gsnet.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 (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. Czechia NIX.CZ Prague, Czechia · PeeringDB 71
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:14::77:1
    Port speed differs10G2G
    • In the entry with IPv4 91.210.16.216: set IPv6 to 2001:7f8:14::77:1 (now empty); set Speed to 2000 (2G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    IPv4 address differs91.213.211.196185.0.20.196
    Port speed differs20G1.25G
    • In the entry with IPv4 91.213.211.196: set IPv4 to 185.0.20.196 (now 91.213.211.196); set Speed to 1250 (1.25G) (now 20000).

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