SkyPass Solutions: PeeringDB fix list

AS202520 · peeringdb.com/net/37413

PeeringDB

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

Make the changes on SkyPass Solutions'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
    Port speed differs2 × 200G2 × 100G
    • In the entry with IPv4 89.46.145.127: set Speed to 100000 (100G) (now 200000).
    • In the entry with IPv4 89.46.145.43: set Speed to 100000 (100G) (now 200000).

    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
    Port speed differs100G50G
    • In the entry with IPv4 212.91.0.46: set Speed to 50000 (50G) (now 100000).
    • Add an entry: IPv4 212.91.0.46, IPv6 –, speed 50000 (50G).

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