Netia: PeeringDB fix list

AS12741 · peeringdb.com/net/5283

PeeringDB

5 things to fix in Netia's PeeringDB record, from what its exchanges publish: 1 to add, 4 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Netia's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in Netia's PeeringDB record. Add one entry per connection with these values.

  1. Ukraine 1-IX UA Kyiv, Ukraine · PeeringDB 3562From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Correct these entries (4)

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs100G200G
    • In the entry with IPv4 80.81.192.193: set Speed to 200000 (200G) (now 100000).
  2. Poland EPIX.Katowice Katowice/Silesia, Poland · PeeringDB 491
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.216.40.240178.216.40.86 178.216.40.240
    IPv6 address missing from PeeringDB2001:7f8:5b::2732001:7f8:5b::86 2001:7f8:5b::273
    Port speed differs100G100G + 10G
    • Add an entry: IPv4 178.216.40.86, IPv6 2001:7f8:5b::86, speed 10000 (10G), RS peer yes.

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

  3. Poland EPIX.Warszawa Warsaw, Poland · PeeringDB 474
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB89.46.144.8889.46.144.88 89.46.144.212
    IPv6 address missing from PeeringDB2001:678:3ac::2402001:678:3ac::212 2001:678:3ac::240
    Port speed differs100G200G + 10G
    • In the entry with IPv4 89.46.144.88: set Speed to 200000 (200G) (now 100000).
    • Add an entry: IPv4 89.46.144.212, IPv6 2001:678:3ac::212, speed 10000 (10G), RS peer yes.

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

  4. Czechia NIX.CZ Prague, Czechia · PeeringDB 71
    ProblemPeeringDB hasThe export has
    Port speed differs100G101G
    • In the entry with IPv4 91.210.17.31: set Speed to 101000 (101G) (now 100000).

    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/12741/: 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.