Baltic Security Monitor | Analytical Brief Snapshot: 11 October 2026, 14:00 (Europe/Tallinn) · Material OSINT Update

Yandex has acknowledged shutting down a third data centre: after Sasovo on 8 October and Kaluga on 9 October, drones hit a facility in Vladimir region. This time the failure was felt beyond the company's own services. The governor reported a fire at an infrastructure facility, two substations disconnected and about 5,000 residents without power. One strike stopped being only a question of computing capacity and became a question of the local power grid.

Assessment

What happened

At 07:16 Moscow time on 11 October Yandex's press service, per Interfax, said that at its Vladimir data centre "infrastructure was damaged as a result of a UAV attack," that its operation is completely halted, that part of its services are unavailable and that there were no casualties. This is the company itself naming a drone. For Sasovo, Yandex used the word "incident." Separately, Yandex Cloud said on Telegram there were "power interruptions" in its ru-central1-a availability zone (Kyiv Independent).

At 08:01 Moscow time Vladimir governor Alexander Avdeyev, per Interfax, reported that a UAV attack hit an infrastructure facility on the outskirts of Vladimir, causing a fire; two substations supplying about 5,000 residents were disconnected; preliminarily no one was hurt and no residential buildings were damaged; people living near the site are being evacuated. The governor does not name the data centre in this statement.

According to Russian media cited by the Kyiv Independent, the disruption hit the Yandex Go taxi service across Russia, Yandex Pro for drivers and couriers, internal company systems and smart-home services. The same report mentions Yandex Go problems in Serbia, Kazakhstan, Belarus and Armenia; that is a report about an app, not a confirmed data-centre failure, and it is not tied to Vladimir.

Ukraine has not claimed this strike. Ukrainian monitoring channels circulated images of a fire near the facility, but the Kyiv Independent could neither verify them nor assess the damage.

BSM analysis

Three sites in four days. Sasovo (8 October, data centre shut down), Kaluga (9 October, "several modules" disabled), Vladimir (11 October, completely shut down). Different regions, one operator, one pattern: drones, fire, services down. The sequence is hard to read as chance, but nobody has confirmed a coordinated campaign. Kyiv has not claimed any of the three, and Zelensky's 8 October remark about responding "in kind" refers to strikes on Ukrainian data centres in general.

What is new in Vladimir: the grid next door. Two substations, 5,000 people and an evacuation near the site show that this time more than a server was affected: local infrastructure was too. The link between the damage to the data centre and the substation outage is not established: the governor speaks of an "infrastructure facility," not a data centre. The explanations differ (a substation feeding the data centre, a fire spreading, separate targets), and open sources cannot choose between them.

What it means for resilience. A cloud lives on moving load between sites. When three go down in four days, and one of them also takes out power, the safety margin shrinks. Yandex has not said how much capacity is lost in total: after Sasovo and Kaluga it said itself that it could not give a timeline for restoring equipment. A claim that Russia's AI sector has been "destroyed" would be premature.

For the Baltic states. The relevance is indirect but practical. Physical strikes on computing sites and their power supply can stop civilian digital services. For critical-infrastructure protection it is a matter of geographic redundancy, independent power and tested recovery plans. It creates no new direct threat to Baltic data centres.

Confirmed versus outstanding

WATCH

🟡 Poland, report of a possible attack on the prime minister and defence minister. New entry. On 11 October Interior Ministry spokeswoman Karolina Galecka said on X that police had received information about a "possible attack" on Donald Tusk and Władysław Kosiniak-Kamysz. Interior Minister Marcin Kierwiński and special-services coordinator Tomasz Siemoniak ordered a response; a meeting was due at 11:00 at the Internal Security Agency's Counter-Terrorism Centre. Radio Zet, per Around Prague, says police received an email; officials have not confirmed that. The nature and origin of the threat are unknown, no suspects are named and no link to any government or group has been established. A report of a threat does not by itself show that an organised operation exists. Context: in September Tusk warned of likely Russian hybrid attacks on NATO's eastern flank; that warning concerned states, not individual politicians. Next check: outcome of the meeting, suspects, arrests, any confirmed foreign involvement.

🟡 US, Ukraine, refineries and intelligence. On 11 October Zelensky wrote on Facebook: "Ukraine will be ready to stop striking Russian oil refineries if Russia stops striking our energy infrastructure," adding that any de-escalation steps must be reciprocal and backed by real guarantees (Ukrinform). The post mentions neither Trump nor intelligence. It is a conditional offer, not an agreement: Russia has made no commitment. The threat to cut off intelligence remains disputed (a Ukrainian official confirms it, an American denies it, Axios); no restrictions have been shown. For the detail and timeline see BSM, 11 October, 08:00. In the same post Zelensky cites a strike on Zaporizhzhia that killed 23 people and a week of about 1,450 guided bombs, 75 missiles and over 1,640 attack drones; those figures are his own.

🟡 Russia, oil infrastructure. Per the digest, Ukraine's General Staff reported another strike on the Samara oil-storage and blending station; at Rostov a fire at the Yug Rusi terminal, with rail traffic restored. No independent confirmation of new damage. Not verified by me.

🟡 Redkino, Ukhta. No new evidence of production losses (per the digest).

🟡 Black Sea. Attribution of the attacks on Alfa Watan and Able is unresolved; Bulgaria confirmed the attacks, with no new forensic conclusion (per the digest).

🟡 RAF Molesworth. The two Latvians remain on bail; no evidence of espionage or Russian intelligence involvement.

🟡 Germany, the Hanning case. The Guardian published further background on 11 October; per the digest it establishes nothing about specific recipients or Allied material. Not verified by me.

🟡 Montenegro, Rybar. The expulsion of Zvinchuk and four Russians remains the latest confirmed action; no results from the examination of the seized equipment.

🟡 Lithuania. No new US base agreement; the constitutional amendment is incomplete.

NATO, Theory of Victory. The presentation is expected on 12 October. Steadfast Noon begins on 13 October; NATO has announced no new nuclear posture.

Other items checked

Per the digest, the Financial Times published new reporting on 11 October on European intelligence warnings about Russian threats to defence-industry executives; it describes no completed attack or operational change, and the topic was covered earlier. AP, per the digest, reported that the death toll of Saturday's strike on Zaporizhzhia rose to 23, including four children; Zelensky also gives 23. I did not check either separately.

Conclusion

Three data centres in four days is no longer an isolated episode but a trend, and its new dimension is that the strike reached the local grid. Two questions remain open: how much computing capacity has really been lost, and whether this is a coordinated campaign. Until there are answers, the most precise statement is what is confirmed: three shutdowns, two official accounts, no claim of responsibility.

Next checks: restoration times at Vladimir and Yandex's other sites; whether the hit on the data centre is tied to the substation outage; further strikes on computing infrastructure and whether Kyiv claims responsibility; the outcome of the Warsaw meetings on the threat to Tusk and Kosiniak-Kamysz; whether Moscow responds to Zelensky's offer of reciprocity.

Baltic Security Monitor (osint-baltic.com) — an analytical publication on security on NATO's northeastern flank. All OSINT assessments are produced by an automated monitoring system using open sources.