ixreport

ZETOZAGAN: PeeringDB fix list

AS202563

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

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

Add these exchanges (2)

On the exchange's own member list, but not in ZETOZAGAN'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.42.100
    IPv62001:7f8:5b::719
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.216.40.239
    IPv62001:7f8:5b::239
    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

    2 connections, so 2 entries:

    IPv489.46.145.168
    IPv62001:678:3ac::642
    Speed10000 Mbps (10G)
    RS peerYes
    IPv489.46.146.11
    IPv62001:678:3ac::654
    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/202563/: 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.