Drone strikes on Yandex data centres disrupt services across Russia and Central Asia
publishers 40articles 54first reported 8 Oct, 09:15 UTCdeveloping since 8 Oct · 14 editions
Three reported Ukrainian drone strikes damaged Yandex data centres in western Russia over four days, forcing shutdowns and disrupting the technology company’s services in Russia and neighboring countries.
The attacks hit facilities in Sasovo in the Ryazan region on Oct. 8, Kaluga on Oct. 9 and Vladimir on Oct. 11. Yandex said the Vladimir centre was completely suspended after sustaining damage, though no one was injured. The company had also described the Sasovo site as seriously damaged and said parts of the Kaluga facility were out of service.
The outages affected services including Yandex Pay, cloud storage, search, maps, smart-home products and the Alisa assistant. Some users could not check balances, transfer money or make purchases. Yandex said it was restoring services gradually and had arranged emergency hosting support from other cloud providers.
Disruption extended to Yandex Go taxi and delivery services in Kazakhstan, where users, drivers and couriers reported problems for about 36 hours. Kazakhstan’s government said local servers holding personal data remained operational, but some service components were hosted abroad. Intermittent problems were also reported in Uzbekistan.
The Kremlin said Tuesday that the Russian government was discussing Yandex’s difficulties, while the company was taking urgent measures to address the damage. Kremlin spokesman Dmitry Peskov said it was too early to determine whether users had suffered financial losses.
Claims that the outages sharply reduced Russian disinformation activity were not supported by Cloudflare data. The widely shared figures tracked automated requests from Yandex systems, including web crawlers, rather than Russian social-media bot activity overall.
HOW THIS STORY WAS MADE
Written from 8 articles, 6 with the publisher's own text; 8 independent newsrooms once syndicated copies count as one; this version written 120 h after the record first saw the story; the editor kept it as written.
- Publishers
- 40
- Source articles
- 54
- Given to the writer
- 8, 6 with the article's own text
- Independent newsrooms
- 8
- This version written
- 120 h after the record first saw the story
- Second model (editor)
- kept as written
- Publication gate
- passed
- Human review
- none
WHAT THE EDITOR DID
The second model checked the writer's draft against the same sources and published it as written.
Written by a language model from the sources above, then checked by a second model that may only cut, attribute or correct. How it works →