Ukraine–Russia
WarTranslated and NOELreports say a Yandex data centre in Kaluga was hit by a UAV attack
This version is a correction.
- Location
- Kaluga, Russia (Yandex data centre not geolocated by the sources; city ±12 km)
- Importance
- Standard
WarTranslated posted that Exilenova+ reported an overnight attack on a Yandex data centre in Kaluga. NOELreports said Yandex confirmed a UAV attack damaged part of the facility and disabled several data-centre modules, while local authorities reported air-defence activity around Kaluga. This is separate from the earlier Yandex data-centre event in Sasovo.
Verification: unverified
Evidence: According to Exilenova+, Yandex’s data center in Kaluga was attacked overnight, A second Yandex data center has been hit, this time in Kaluga
The recovered material is from X posts and is treated as attributed/unverified unless explicitly described as an official claim relayed by the post.
- According to Exilenova+, Yandex’s data center in Kaluga was attacked overnightWarTranslated · Social post · supports · Published 09 Oct 2026, 07:41 UTC · Retrieved 09 Oct 2026, 10:38 UTC
- A second Yandex data center has been hit, this time in KalugaNOELREPORTS · Social post · supports · Published 09 Oct 2026, 07:58 UTC · Retrieved 09 Oct 2026, 10:38 UTC
Classification
Military · Airstrike · DRONE · Atomic
Tags: data_center · kaluga · yandex
Location methodology
Kaluga, Russia (Yandex data centre not geolocated by the sources; city ±12 km) · within 12 km · Confidence: Estimated · Evidence: According to Exilenova+, Yandex’s data center in Kaluga was attacked overnight, A second Yandex data center has been hit, this time in Kaluga
Claims
- The accounts said a Yandex data centre in Kaluga was attacked overnight and that several modules were disabled. · Attributed to WarTranslated and NOELreports · Confidence: Unknown · Evidence: According to Exilenova+, Yandex’s data center in Kaluga was attacked overnight, A second Yandex data center has been hit, this time in Kaluga
Review and provenance
Revision 2 · First published 09 Oct 2026, 10:38 UTC · Current revision 09 Oct 2026, 13:54 UTC · Change: Correction