ixreport

Yandex Cloud

AS200350

Yandex.Cloud LLC

11Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
EnterpriseType
OpenPeering policy
11Using the route servers
3Facilities in PeeringDB

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

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

PeeringDB fix list

Nothing to fix: Yandex Cloud's PeeringDB record matches the member lists of the 2 exchanges we could compare (the others publish no list we could read).

Exchanges over time

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

Map

Where Yandex Cloud'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 2.6T across 11 exchanges.

Russia CLOUD-IX MSK Moscow, Russia 31.28.19.20 2a00:13c0:3:1::1f1c:1314 100G Yes PeeringDB
Russia Eurasia Peering IX Moscow, Russia 185.232.60.241 2a0d:e180::60:241 100G Yes PeeringDB
Netherlands Global-IX Amsterdam, Netherlands 109.239.136.62
109.239.136.69
2001:b28:3ff::4f7e:0:1
2001:b28:3ff::4f7e:1:1
2 × 200G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.227.3
178.18.227.9
2a03:5f80:4::227:3
2a03:5f80:4::227:9
2 × 200G Yes Both
Russia MSK-IX Moscow Moscow, Russia 195.208.208.145
195.208.209.51
2001:7f8:20:101::208:145
2001:7f8:20:101::209:51
2 × 200G Yes Both
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.186.216 200G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.95 200G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.13.171 2001:7f8:eb::3:e9e:1 200G Yes PeeringDB
Latvia PITER-IX Riga Riga, Latvia 193.27.39.162 200G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.126 2001:7f8:e6::3:e9e:1 200G Yes PeeringDB
Estonia PITER-IX Tallinn Tallinn, Estonia 37.9.49.130 200G Yes PeeringDB

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

These exchanges have a switch in a facility where Yandex Cloud lists itself in PeeringDB, but don't have Yandex Cloud 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 W-IXMoscow, Russia 66 Moscow M9; Moscow TehnoGorod
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (3)

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

Russia Moscow M9Moscow 7 of 9
Russia StoreDataMoscow 4 of 4
Russia Moscow TehnoGorodMoscow 2 of 3