ixreport

Luganet

AS39728

12Exchanges
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
12Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

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

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Luganet's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-11-19 12:40 UTC.

Make the changes on Luganet's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Check these entries (1)

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

  1. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107Not on its IX-F export
    IPv4194.226.100.62
    IPv6–
    Speed100000 Mbps (100G)
    IPv4194.226.102.62
    IPv6–
    Speed100000 Mbps (100G)

Exchanges over time

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

Map

Where Luganet'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 1.8T across 12 exchanges.

Netherlands Global-IX Amsterdam, Netherlands 109.239.136.104 100G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.18
178.18.226.227
2a03:5f80:4::225:18
2a03:5f80:4::226:227
2 × 100G Yes Both
Russia M-IX Simferopol, Russia 193.34.200.224 100G Yes PeeringDB
Russia MSK-IX Moscow Moscow, Russia 195.208.208.71 100G Yes Both
Russia MSK-IX Rostov-on-Don Rostov-on-Don, Russia 193.232.140.51 20G Yes Both
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.62
194.226.102.62
2 × 100G Yes PeeringDB only
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.186.147 200G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.220 200G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.13.198 200G Yes PeeringDB
Russia PITER-IX Rostov Rostov, Russia 193.27.38.34 200G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.152.207 200G Yes PeeringDB
Russia Sea-IX Krasnodar, Russia 91.240.225.204 100G Yes PeeringDB

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

These exchanges have a switch in a facility where Luganet lists itself in PeeringDB, but don't have Luganet 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.

Russia Eurasia Peering IXMoscow, Russia 136 Moscow M9
Russia W-IXMoscow, Russia 66 Moscow M9
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (2)

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

Russia Moscow M9Moscow 5 of 9
Russia РТКомм-Юг (RTKomm-Yug)Rostov-on-Don 1 of 1