ixreport

PIEKARY.NET: PeeringDB fix list

AS42266 · peeringdb.com/net/11166

PeeringDB

One thing to fix in PIEKARY.NET's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on PIEKARY.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 (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. Poland EPIX.Katowice Katowice/Silesia, Poland · PeeringDB 491
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.216.40.10178.216.40.10 178.216.40.123
    IPv6 address missing from PeeringDBnone2001:7f8:5b::10 2001:7f8:5b::123
    Port speed differs10G2 × 10G
    • In the entry with IPv4 178.216.40.10: set IPv6 to 2001:7f8:5b::10 (now empty).
    • Add an entry: IPv4 178.216.40.123, IPv6 2001:7f8:5b::123, 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.

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