ixreport

ATLEX.RU

AS199669 · ATLEX.RU

Okay-Telecom Ltd.

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

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

Make the changes on ATLEX.RU'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 ATLEX.RU 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.153
    IPv62001:7f8:20:201::100:153
    Speed10000 Mbps (10G)
    IPv4194.226.102.153
    IPv62001:7f8:20:202::102:153
    Speed10000 Mbps (10G)

Exchanges over time

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

Map

Where ATLEX.RU'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 50G across 4 exchanges.

Netherlands Global-IX Amsterdam, Netherlands 109.239.136.159 2001:b28:3ff::4dfe:0:1 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.227.84 2a03:5f80:4::227:84 10G Yes Both
Russia MSK-IX Moscow Moscow, Russia 195.208.208.153 2001:7f8:20:101::208:153 10G Yes Both
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.153
194.226.102.153
2001:7f8:20:201::100:153
2001:7f8:20:202::102:153
2 × 10G Yes PeeringDB only

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

These exchanges have a switch in a facility where ATLEX.RU lists itself in PeeringDB, but don't have ATLEX.RU 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 PITER-IX MoscowMoscow, Russia 243 Moscow M9
Russia Eurasia Peering IXMoscow, Russia 136 Moscow M9
Russia W-IXMoscow, Russia 66 Moscow M9
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9; DataPro Moscow
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (3)

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

Russia Moscow M9Moscow 3 of 9
Russia DataPro MoscowMoscow 2 of 3
Russia ATLEX.RUMoscow No exchange