Russia
50 of 61 facility records have a location.
Power on record
Facilities
| Yandex Chervonenkis | Yandex, AI hardware owner | 1 | 1,592 |
|---|---|---|---|
| Yandex Lyapunov | Yandex, AI hardware owner | 0.9 | 1,096 |
| Yandex Galushkin | Yandex, AI hardware owner | 0.9 | 1,088 |
| Moscow State University Lomonosov 2 | Moscow State Univeristy, AI hardware owner | 0.9 | 1,472 |
| SberCloud Christofari | Sbercloud, AI hardware owner | 0.8 | 1,200 |
| SberCloud Christofari Neo | Sbercloud, AI hardware owner | 0.7 | 792 |
| MTS Grom | Mts, AI hardware owner | 0.1 | 160 |
| Bolshaya Morskaya 18 | SPBIX, PeeringDB listing holder | ||
| COD BM-18 | Center data exchange, PeeringDB listing holder | ||
| CSS MPS Moscow | CSS MPS Moscow, PeeringDB listing holder | ||
| Data Harbour | |||
| Data-Center IMAQLIQ | IMAQLIQ SERVICE Ltd, PeeringDB listing holder | ||
| DataCenter Three Seven | |||
| DataHouse Moscow | Filanco Ltd., PeeringDB listing holder | ||
| DataLine Moscow 1 | LLC Dataline, PeeringDB listing holder | ||
| DataLine Moscow 2 | LLC Dataline, PeeringDB listing holder | ||
| DataPro Moscow | "DATAPRO" Limited Liability Company, PeeringDB listing holder | ||
| DataPro V | DataPro, Site operator | ||
| DataSpace Moscow | DataSpace Partners LLC, PeeringDB listing holder | ||
| EKB, Uralcod | Uralskiy center obrabotki dannikh, PeeringDB listing holder | ||
| Erlang.Ekb.MS145 | Erlang company Ltd., PeeringDB listing holder | ||
| GreenBushDC | Mts, Site operator | ||
| IVC ORW Saint-Petersburg | JSC "Russian Railways", "October Railway", PeeringDB listing holder | ||
| IXcellerate MOS1 | IXcellerate LLC, PeeringDB listing holder | ||
| IXcellerate North MOS 1 | IXcellerate, Site operator | ||
| Key Point | Key Point, Site operator | ||
| Linxdatacenter (Moscow) | Linxdatacenter, PeeringDB listing holder | ||
| Linxdatacenter (Saint-Petersburg) | Linxdatacenter, PeeringDB listing holder | ||
| M1 StackTelecom Datacenter | |||
| Miran-1 | Miran Ltd, PeeringDB listing holder | ||
| Miran-2 | Miran Ltd, PeeringDB listing holder | ||
| Moscow M10 | Rostelecom, PeeringDB listing holder | ||
| Moscow M9 | MMTS-9 JSC, PeeringDB listing holder | ||
| Moscow TehnoGorod | TehnoGorod, PeeringDB listing holder | ||
| MSK-IX | |||
| MSU-270 | Moscow State Univeristy, AI hardware owner | 100 | |
| NORD-1 | |||
| NORD-2 | |||
| NORD-3 | |||
| NORD-4 | DataLine, Site operator | ||
| NORD-5 | |||
| NORD-6 | |||
| Raduga-2 | Raduga-2, PeeringDB listing holder | ||
| RETNNet OV DC | RETN, PeeringDB listing holder | ||
| Rostelecom Ekaterinburg | Rostelecom, Site operator | ||
| Rostelecom Nizhny Novgorod | Rostelecom, Site operator | ||
| Rostelecom Novosibirsk | Rostelecom, Site operator | ||
| Selectel | |||
| Selectel Berzarina | Selectel, Site operator | ||
| Sinar | NvsF FSUE "TsentrInform", PeeringDB listing holder | ||
| Stack.M1 | Stack Group, PeeringDB listing holder | ||
| StoreData | StoreData LLC, PeeringDB listing holder | ||
| Telehouse Saint Petersburg | |||
| Tsvetochnaya Data Center | Selectel Ltd., PeeringDB listing holder | ||
| Web Data Center | |||
| Xelent | Atomdata-Center Xelent, PeeringDB listing holder | ||
| Дата-центр SDN | |||
| Дата-центр Миран-2 | |||
| Мегафон | |||
| РТКомм-Юг (RTKomm-Yug) | RTKomm-Yug, PeeringDB listing holder | ||
| ЦОД "Дубровка-1" | Selectel, Site operator |
Ownership
0% of operating power is traced to a company with an SEC identifier or a linked parent.
Facilities by ownership tier
Open a facility for its ownership relationships and sources.
Ownership tiers over time
Operating-capacity-weighted shares at each recorded snapshot. Dates are when the distribution was captured; the ownership evidence can be older.
42 snapshots weighted by operating capacity, from 2026-09-23 to 2026-11-03. 144 earlier snapshots weighted every recorded power figure and are listed under Snapshot values.
- Tier 1 — company has an SEC identifier or a parent linked through filing, registry or supply-chain data
- Tier 2 — parent linked through licensed ownership data
- Tier 3 — parent linked through other sources
- Tier 4 — company identified; parent unrecorded
- Data Gap — no company linked
Snapshot values
Displayed MW are rounded to two decimal places. Operating capacity counts operational records only; a snapshot taken before operating weighting began lists only the figure it recorded, every status summed. Download values (JSON) for the full inputs used to calculate the shares. Consecutive snapshots showing the same figures are listed once, under their first and last dates; the download keeps every date.
2026-04-25 – 2026-05-05 · 10 snapshots
5.72 MW recorded, every status · 61 facilities
- Tier 1 — company has an SEC identifier or a parent linked through filing, registry or supply-chain data
- 0 MW · 0 facilities · 0.0%
- Tier 2 — parent linked through licensed ownership data
- 0 MW · 1 facility · 0.0%
- Tier 3 — parent linked through other sources
- 0 MW · 0 facilities · 0.0%
- Tier 4 — company identified; parent unrecorded
- 5.72 MW · 49 facilities · 100.0%
- Data Gap — no company linked
- 0 MW · 11 facilities · 0.0%
2026-05-06 – 2026-05-10 · 5 snapshots
5.72 MW recorded, every status · 61 facilities
- Tier 1 — company has an SEC identifier or a parent linked through filing, registry or supply-chain data
- 0 MW · 0 facilities · 0.0%
- Tier 2 — parent linked through licensed ownership data
- 0 MW · 1 facility · 0.0%
- Tier 3 — parent linked through other sources
- 0 MW · 0 facilities · 0.0%
- Tier 4 — company identified; parent unrecorded
- 5.72 MW · 45 facilities · 100.0%
- Data Gap — no company linked
- 0 MW · 15 facilities · 0.0%
2026-05-11 – 2026-09-22 · 129 snapshots
5.72 MW recorded, every status · 61 facilities
- Tier 1 — company has an SEC identifier or a parent linked through filing, registry or supply-chain data
- 0 MW · 0 facilities · 0.0%
- Tier 2 — parent linked through licensed ownership data
- 0 MW · 0 facilities · 0.0%
- Tier 3 — parent linked through other sources
- 0 MW · 0 facilities · 0.0%
- Tier 4 — company identified; parent unrecorded
- 5.72 MW · 46 facilities · 100.0%
- Data Gap — no company linked
- 0 MW · 15 facilities · 0.0%
2026-09-23 – 2026-11-03 · 42 snapshots
5.72 MW operating · 61 facilities
- Tier 1 — company has an SEC identifier or a parent linked through filing, registry or supply-chain data
- 0 MW · 0 facilities · 0.0%
- Tier 2 — parent linked through licensed ownership data
- 0 MW · 0 facilities · 0.0%
- Tier 3 — parent linked through other sources
- 0 MW · 0 facilities · 0.0%
- Tier 4 — company identified; parent unrecorded
- 5.72 MW · 46 facilities · 100.0%
- Data Gap — no company linked
- 0 MW · 15 facilities · 0.0%
Export controls
1,087 Entity List designations against organisations located here.
The rules retain specified case-by-case review pathways and narrow license exceptions.
Chip-specific conditions and sources
- A100
- Embargoed
- H100
- Embargoed
- H200
- Embargoed
- B200
- Embargoed
- MI300X
- Embargoed
EAR 746.8 requires licenses for items subject to the EAR and listed on the Commerce Control List. Paragraph (b) provides the review policy, including specified case-by-case purposes and recipients; paragraph (c) lists narrow exceptions.
Access routes and alternatives
- Third party
- An electronics-diversion precedent: Nikolay Goltsev was sentenced in January 2025 for a scheme that routed US components to Russia through intermediary companies, including in Turkey and the UAE.DOJ identified components used in Russian weapons. This case does not establish advanced-AI-GPU procurement or quantify compute capacity.US Department of Justice, 8 Jan 2025
Chip industry. Baikal Electronics describes itself as a Russian fabless developer of processors and microcontrollers.
Sources: Russia and Belarus licensing requirements and review policies; Baikal Electronics company profile.
Organisations
All 2 organisations
| Moscow Institute of Physics and Technology | ||
|---|---|---|
| Yandex |
Related pages
Sources
4 sources
- Epoch AI frontier data centers and GPU clusters: https://epoch.ai/data/data-centers
- Export-control rules (US EAR, Dutch and Japanese regimes): https://scrutica.com/export-controls/countries
- BIS Entity List via the Consolidated Screening List and the Federal Register: https://www.federalregister.gov/
- Sovereign AI programme register: https://scrutica.com/sovereign-ai
How the figures were made
Geography. Outlines use Natural Earth de facto boundaries. Distant parts may be omitted; located records outside the drawing are counted in its caption. Power circles use the same scale across countries.
Counts. Counts retrieved 3 Nov 2026. Operating capacity and ownership shares include estimated capacity; a campus figure recorded as its full build-out, earlier phases and second records are shown apart rather than counted. Sovereign programme ratios use government-only announced amounts where available; each ratio lists its numerator and denominator.
Corporate traceability. No company linked means no operator, site owner or hardware owner has been linked to the facility. The tiers do not verify property ownership or facility operation. Announced and under-construction figures are not counted here. Tiers classify the available sources for a company linked to each facility. A linked company’s SEC identifier can qualify it for the first tier without establishing a parent. Ownership relationships and their sources are listed on the facility and company pages.
Export-control posture. Recipient and end-use conditions can change the outcome of a transaction. Classification review: 17 Jul 2026. Access basis: 0.00. The value encodes the embargoed access category. The sources recorded here do not quantify installed AI compute or capacity obtained through intermediaries. Russia and Belarus sanctions, EAR 746.8.
Organisations headquartered here. Across all industries; multiple identifiers may refer to the same company. The record lists 2 distinct organisations with qualifying market-capitalisation or linked-record evidence, after reviewing all public organisation rows for Russia; the source holds 133 organisation rows, including duplicate identities and rows without qualifying evidence, and the company register applies its own evidence scope. A type is shown only where the classification has been reviewed.
Corrections to this page, 2
Identifiers
- ISO country code
- RU