ixreport

Kireshki: PeeringDB fix list

AS214946 · peeringdb.com/net/36332

PeeringDB

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

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

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

  1. Netherlands Frys-IX Fryslân, Netherlands · PeeringDB 3512From its IX-F export
    IPv4–
    IPv62001:7f8:10f::3:47a2:128
    Speed10000 Mbps (10G)
    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. Netherlands INTERIX Amsterdam, Netherlands · PeeringDB 3990From its IX-F export and website members list
    IPv4185.1.184.79
    IPv62001:7f8:134::3f
    Speed10000 Mbps (10G)
    RS peerYes

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

  3. Canada ONIX Toronto, Canada · PeeringDB 4059From its IX-F export and website members list
    IPv4149.112.50.119
    IPv62001:504:125:e1::119
    Speed1000 Mbps (1G)
    RS peerYes

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