ixreport

MATRIXKURO: PeeringDB fix list

AS204522

3 things to fix in MATRIXKURO's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-10-08 18:53 UTC.

AS204522 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (3)

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

  1. Poland EPIX.Katowice Katowice/Silesia, Poland · PeeringDB 491From its IX-F export
    IPv4178.216.42.82
    IPv62001:7f8:5b::641
    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

    3 connections, so 3 entries:

    IPv489.46.145.57
    IPv62001:678:3ac::309
    Speed10000 Mbps (10G)
    RS peerYes
    IPv489.46.145.166
    IPv62001:678:3ac::539
    Speed10000 Mbps (10G)
    RS peerYes
    IPv489.46.145.250
    IPv62001:678:3ac::638
    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.

  3. Poland TPIX PL Warsaw, Poland · PeeringDB 482From its IX-F export and website members list
    IPv4195.149.232.223
    IPv6–
    SpeedNot published
    RS peerNot published

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