KONFER: PeeringDB fix list

AS50953 · peeringdb.com/net/21112

PeeringDB

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

Make the changes on KONFER'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 Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:7f::c:23
    Port speed differs10G1.25G
    • In the entry with IPv4 185.0.21.23: set IPv6 to 2001:7f8:7f::c:23 (now empty); set Speed to 1250 (1.25G) (now 10000).
  2. Slovakia SIX.SK Bratislava, Slovakia · PeeringDB 84
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 192.108.148.82: set Speed to 20000 (20G) (now 10000).

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

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