ixreport

Connected sp. z o.o.: PeeringDB fix list

AS49102 · peeringdb.com/net/9622

PeeringDB

2 things to fix in Connected sp. z o.o.'s PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 21:56 UTC.

Make the changes on Connected sp. z o.o.'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 Connected sp. z o.o.'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.40.115
    IPv62001:7f8:5b::115
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.216.41.105
    IPv62001:7f8:5b::361
    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 TPIX PL Warsaw, Poland · PeeringDB 482From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4–
    IPv62001:7f8:27::4:9102:2
    SpeedNot published
    RS peerNot published
    IPv4195.149.232.189
    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/49102/: 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.