ixreport

COOLNET LLC: PeeringDB fix list

AS212372 · peeringdb.com/net/25165

PeeringDB

3 things to fix in COOLNET LLC's PeeringDB record, from what its exchanges publish: 2 to add, 1 to check. As of 2026-10-08 18:53 UTC.

Make the changes on COOLNET LLC'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 (2)

On the exchange's own member list, but not in COOLNET LLC's PeeringDB record. Add one entry per connection with these values.

  1. Germany KleyReX Frankfurt, Germany · PeeringDB 123From its IX-F export and website members list
    IPv4193.189.83.110
    IPv62001:7f8:33::a121:2372:1
    Speed100 Mbps (100M)
    RS peerYes

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

  2. Ukraine RUDAKI-IX Kiev, Ukraine · PeeringDB 3681From its IX-F export
    IPv4185.1.225.63
    IPv62001:7f8:11f:1:0:212:372:1
    Speed10000 Mbps (10G)
    RS peerNot published

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If COOLNET LLC has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Ukraine 1-IX UA Kyiv, Ukraine · PeeringDB 3562Not on its website members list
    IPv4185.1.213.184
    IPv62001:7f8:14d::184
    Speed20000 Mbps (20G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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