WIST: PeeringDB fix list

AS56709 · peeringdb.com/net/25332

PeeringDB

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

Make the changes on WIST'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 WIST's PeeringDB record. Add one entry per connection with these values.

  1. Poland EPIX.Warszawa Warsaw, Poland · PeeringDB 474From its IX-F export
    IPv489.46.144.92
    IPv62001:678:3ac::92
    Speed10000 Mbps (10G)
    RS peerYes

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

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
    Port speed differs10G20G
    • In the entry with IPv4 178.216.41.242: 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/56709/: 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.