ixreport

Lekol

AS50115 · Westelecom

Lekol LLC

6Exchanges
1On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
1Using the route servers
2To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with Lekol? · Where should Lekol peer next? · Compare Lekol with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in Lekol's PeeringDB record, from what its exchanges publish: 1 to add, 1 to check. As of 2026-11-19 12:40 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.

Exchanges over time

0246Oct 3, 2026Nov 19, 20266
Show as a table
DateExchanges
Nov 19, 20266
Nov 18, 20266
Nov 17, 20266
Nov 16, 20266
Nov 15, 20266
Nov 14, 20266
Nov 13, 20266
Nov 12, 20266
Nov 11, 20266
Nov 10, 20266
Nov 9, 20266
Nov 8, 20266
Nov 7, 20266
Nov 6, 20266
Nov 5, 20266
Nov 4, 20266
Nov 3, 20266
Nov 2, 20266
Nov 1, 20266
Oct 31, 20266
Oct 30, 20266
Oct 29, 20266
Oct 28, 20266
Oct 27, 20266
Oct 26, 20266
Oct 25, 20266
Oct 24, 20266
Oct 23, 20266
Oct 22, 20266
Oct 21, 20266
Oct 20, 20266
Oct 19, 20266
Oct 18, 20266
Oct 17, 20266
Oct 16, 20266
Oct 15, 20266
Oct 14, 20266
Oct 13, 20266
Oct 12, 20266
Oct 11, 20266
Oct 10, 20266
Oct 9, 20266
Oct 8, 20266
Oct 7, 20266
Oct 6, 20266
Oct 5, 20266
Oct 4, 20266
Oct 3, 20266

Map

Where Lekol's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 140G across 6 exchanges.

Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 185.0.42.84 20G Both
Ukraine 1-IX UA Kyiv, Ukraine 185.1.213.84 20G PeeringDB only
Ukraine Giganet IXN Amsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine 185.1.62.118 40G PeeringDB
Ukraine Giganet IXN Odesa Odessa, Ukraine 193.34.196.140 40G PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.230.188 2a03:5f80:7::230:188 10G Yes Not in PeeringDB
Ukraine GNM-IX UA Kiev, Ukraine 178.18.230.188 10G PeeringDB

Exchanges in its buildings that it isn't on (4)

These exchanges have a switch in a facility where Lekol lists itself in PeeringDB, but don't have Lekol as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Ukraine DTEL-IXKiev, Ukraine 204 OD-IX
Ukraine RUDAKI-IXKiev, Ukraine 53 OD-IX
Poland Giganet IXN WarsawWarsaw, Poland 49 OD-IX
Ukraine Giganet IXN KharkіvKharkiv, Ukraine 13 OD-IX
Facilities (1)

The buildings Lekol lists in PeeringDB, and how many of the exchanges in each it's on.

Ukraine OD-IXOdesa 3 of 7