Datacenter reachability Minute-by-minute network checks of Russia's largest datacenters

Once a minute we open a TCP connection to public addresses that open sources tie to a specific site. Probes run from Finland: Russian filtering and cuts to international links can look like an outage, so control hosts inside Russia are checked alongside.

These are not confirmed incidents: a cell on the card is crossed out only on a public source.

Last check: 22.10.2026 23:35 UTC. Control hosts in Russia: 40 of 40 answering. reachable: 10

Control hosts in Russia (8)
#DatacenterNow 24 hoursms
1 IXcellerate MOS5Moscow · IXcellerate reachable 38
What we check (1)
  • mgw01.ixcellerate.ru:25 — IXcellerate mail gateway on AS48807 (PeeringDB: only at MOS5) · 37 ms · why this address
19 DataPro Moscow IMoscow · DataPro reachable 35
What we check (1)
  • billing.firstbyte.ru:443 — FirstByte (all servers at DataPro, Aviamotornaya 69) · 35 ms · why this address
21 OXYGEN MSK-1Moscow · OXYGEN reachable 56
What we check (2)
  • ksmg.o2xygen.ru:25 — OXYGEN mail gateway on AS208349 · 38 ms · why this address
  • oxygen.cloud:443 — OXYGEN site on its own AS208349 · 63 ms · why this address
31 Linx St PetersburgSt Petersburg · Linx reachable 42
What we check (1)
  • linx-ping-test.ruvds.com:28789 — RUVDS ping-test server, Linxdatacenter SPb · 38 ms · why this address
36 Selectel Tsvetochnaya-2St Petersburg · Selectel reachable 16
What we check (1)
  • 188.124.38.132:80 — Selectel RIPE Atlas anchor (Tsvetochnaya campus) · 13 ms · why this address
40 DataSpaceMoscow · DataSpace reachable 64
What we check (2)
  • ksmg1.dataspace.ru:25 — DataSpace mail gateway on AS209930 · 37 ms · why this address
  • www.dataspace.ru:443 — DataSpace site on its own AS209930 · 37 ms · why this address
57 Selectel Tsvetochnaya-1St Petersburg · Selectel reachable 15
What we check (1)
  • 188.124.38.132:80 — Selectel RIPE Atlas anchor (Tsvetochnaya campus) · 16 ms · why this address
60 Stack Kazan (STACK 24)Kazan · Stack Group reachable 91
What we check (1)
  • stack24.ru:443 — Stek Kazan site on its own AS60651 (single DC) · 88 ms · why this address
61 Key Point VladivostokVolno-Nadezhdinskoye · Key Point reachable 140
What we check (1)
  • 94.247.105.254:443 — Truenetwork S3 Vladivostok (KEYPOINT-VLD) · 142 ms · why this address
74 Stack.M1Moscow · Stack Group reachable 43
What we check (1)
  • lk.stacktelecom.ru:443 — M1Cloud portal, M1_CLOUD net (has DR sites) · 44 ms · why this address

Not monitored (65)

Operational datacenters with no public address reliably tied to the site (mostly Yandex, VK and Sber in-house sites).

Yandex Kaluga, Yandex Sasovo, Yandex Vladimir, Kalininsky DC, Yandex Vladimir-2, RTK-DC Medvedkovo-2, Atomdata Moskva-2, 3data HyperScale Medvedkovo, RTK-DC Medvedkovo-1, Sber MegaDC Skolkovo, IXcellerate MOS3, DataPro Moscow III, RTK-DC NORD (DataLine), Key Point Dubna-M, RTK-DC Ostapovsky (Moscow-I, V), MWS Avantazh, VK ITsVA, Sber Yuzhny Port, MWS Fedorovsky, DataHouse Magistralny-1, VK Pakhra-2, MegaFon St Petersburg, Yandex Ivanteevka, Yandex Mytishchi, IXcellerate MOS1, RTK-DC OST (DataLine), IXcellerate MOS2, MWS GreenBushDC, Key Point Yekaterinburg, DataPro Moscow II, Selectel Berzarina, Atomdata Xelent, RTK-DC Kurchatovsky (Moscow-II, III), DataHouse Mednaya Folga, DataPro Moscow IV, MegaFon Samara, Atomdata Innopolis, CROC Kompressor, MWS Nizhny Novgorod, RTK-DC St Petersburg, IXcellerate MOS4, Key Point Novosibirsk, RTK-DC Yekaterinburg-3, Goznak St Petersburg, VK Pakhra-1, Goznak Moscow, RTK-DC Nizhny Novgorod, Linx Moscow, MegaFon Moscow (Technopolis), RTK-DC Novosibirsk, Selectel Dubrovka-1, Selectel Dubrovka-2, Selectel Dubrovka-3, Stack.HTH, MWS Novosibirsk, MegaFon Dmitrov, Atomdata StoreData, MegaFon Tver, MegaFon Yekaterinburg, MegaFon Khabarovsk, Stack.P1, MWS Krasnodar, MWS Vladivostok, MWS Samara, Beeline Yaroslavl