ixreport

Selectel MSK

AS50340 · Selectel Network of DataCenters

Selectel Ltd.

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

Tools: Where can I peer with Selectel MSK? · Where should Selectel MSK peer next? · Compare Selectel MSK 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 Selectel MSK's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-11-19 12:40 UTC.

Make the changes on Selectel MSK'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 Selectel MSK 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.55
    IPv62001:7f8:20:201::100:55
    SpeedNot published
    IPv4194.226.102.55
    IPv62001:7f8:20:202::102:55
    SpeedNot published

Exchanges over time

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

Map

Where Selectel MSK'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 850G, at the 6 of 7 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.209.85 2001:7f8:1::a505:340:1 10G Up, 0 routes Both
Netherlands Global-IX Amsterdam, Netherlands 109.239.137.217 2001:b28:3ff::c4a4:0:1 200G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.224.197 2a03:5f80:4::224:197 300G Yes Both
Russia MSK-IX Moscow Moscow, Russia 195.208.209.162 2001:7f8:20:101::209:162 200G Yes Both
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.55
194.226.102.55
2001:7f8:20:201::100:55
2001:7f8:20:202::102:55
Yes PeeringDB only
Russia PITER-IX Moscow Moscow, Russia 185.0.15.8 2001:7f8:eb::c4a4:1 100G Yes PeeringDB
Russia W-IX Moscow, Russia 193.106.113.30 2a00:1b30::1:30 40G Yes PeeringDB

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

These exchanges have a switch in a facility where Selectel MSK lists itself in PeeringDB, but don't have Selectel MSK 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 PITER-IX Saint-PetersburgSaint-Petersburg, Russia 246 Moscow M9
Russia Eurasia Peering IXMoscow, Russia 136 Moscow M9
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (2)

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

Russia Moscow M9Moscow 5 of 9
Russia Berzarina Data CenterMoscow No exchange