ixreport

ITCare Pawel Staszewski: PeeringDB fix list

AS198560 · peeringdb.com/net/12139

2 things to fix in ITCare Pawel Staszewski's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on ITCare Pawel Staszewski'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 ITCare Pawel Staszewski'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.145.137
    IPv62001:678:3ac::a137
    Speed100000 Mbps (100G)
    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
    IPv4 address missing from PeeringDB178.216.40.112178.216.40.112 178.216.40.138
    IPv6 address missing from PeeringDB2001:7f8:5b::1122001:7f8:5b::112 2001:7f8:5b::169
    Port speed differs1G100G + 1G
    • Add an entry: IPv4 178.216.40.138, IPv6 2001:7f8:5b::169, speed 100000 (100G), RS peer yes.

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