ixreport

Polineo Sp. z o.o.: PeeringDB fix list

AS204373 · peeringdb.com/net/13528

PeeringDB

3 things to fix in Polineo Sp. z o.o.'s PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Polineo 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 (1)

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

  1. Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Correct these entries (2)

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
    IPv6 address missing from PeeringDBnone2001:7f8:5b::406
    • In the entry with IPv4 178.216.41.151: set IPv6 to 2001:7f8:5b::406 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. Poland EPIX.Warszawa Warsaw, Poland · PeeringDB 474
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:678:3ac::104 2001:678:3ac::227
    • In the entry with IPv4 89.46.144.104: set IPv6 to 2001:678:3ac::104 (now empty).
    • In the entry with IPv4 89.46.144.227: set IPv6 to 2001:678:3ac::227 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

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