ixreport

Derkom Spolka: PeeringDB fix list

AS197697 · peeringdb.com/net/11975

PeeringDB

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

Make the changes on Derkom Spolka'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.Warszawa Warsaw, Poland · PeeringDB 474
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:678:3ac::315
    • In the entry with IPv4 89.46.145.63: set IPv6 to 2001:678:3ac::315 (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 THINX Warsaw Warsaw, Poland · PeeringDB 481
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:60::19:7697:1
    • Add an entry: IPv4 –, IPv6 2001:7f8:60::19:7697:1, speed 10000 (10G).

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