ixreport

Lekol: PeeringDB fix list

AS50115 · peeringdb.com/net/16956

PeeringDB

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

Make the changes on Lekol'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 (1)

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

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

    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 Lekol 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.84
    IPv6–
    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/50115/: 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.