ixreport

INFONET: PeeringDB fix list

AS205105 · peeringdb.com/net/25527

PeeringDB

2 things to fix in INFONET's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 22:13 UTC.

Make the changes on INFONET'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 (2)

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

  1. Poland EPIX.Katowice Katowice/Silesia, Poland · PeeringDB 491From its IX-F export

    2 connections, so 2 entries:

    IPv4178.216.41.226
    IPv62001:7f8:5b::457
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.216.40.81
    IPv62001:7f8:5b::81
    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.

  2. Poland EPIX.Warszawa Warsaw, Poland · PeeringDB 474From its IX-F export
    IPv489.46.145.151
    IPv62001:678:3ac::524
    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.

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