ixreport

Dolnet Group: PeeringDB fix list

AS198498 · peeringdb.com/net/25541

PeeringDB

2 things to fix in Dolnet Group's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Dolnet Group's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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::306 2001:7f8:5b::307
    • In the entry with IPv4 178.216.41.50: set IPv6 to 2001:7f8:5b::306 (now empty).
    • In the entry with IPv4 178.216.41.51: set IPv6 to 2001:7f8:5b::307 (now empty).

    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 474
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:678:3ac::40 2001:678:3ac::41
    • In the entry with IPv4 89.46.144.40: set IPv6 to 2001:678:3ac::40 (now empty).
    • In the entry with IPv4 89.46.144.41: set IPv6 to 2001:678:3ac::41 (now empty).

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