OptiKabel Telecom: PeeringDB fix list

AS201966 · peeringdb.com/net/25317

PeeringDB

3 things to fix in OptiKabel Telecom's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on OptiKabel Telecom'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 (3)

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 PeeringDB2001:7f8:5b::6692001:7f8:5b::270 2001:7f8:5b::669
    Port speed differs40G + 10G2 × 40G
    • In the entry with IPv4 178.216.41.46: set IPv6 to 2001:7f8:5b::270 (now empty); set Speed to 40000 (40G) (now 10000).

    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
    Port speed differs10G40G
    • In the entry with IPv4 89.46.144.204: set Speed to 40000 (40G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  3. Poland THINX Warsaw Warsaw, Poland · PeeringDB 481
    ProblemPeeringDB hasThe export has
    Port speed differs10G5G
    • In the entry with IPv4 212.91.0.55: set Speed to 5000 (5G) (now 10000).
    • Add an entry: IPv4 212.91.0.55, IPv6 –, speed 5000 (5G).

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