Yandex Drone Strikes: 3 Data Centers Hit in 4 Days

Three drone strikes in four days have knocked pieces of Yandex’s data center network offline, disrupting cloud services and leaving users of the company’s ride-hailing and payment apps reporting outages across Russia. The Register flagged the pattern on October 12, 2026, tying together a string of incidents that Yandex itself has confirmed in a series of brief statements since October 8. The company has not said when full operations will resume at any of the three sites.

What makes this story different from the usual cadence of wartime infrastructure headlines is the target. Yandex is not a power substation or a rail junction. It is Russia’s largest search engine, its biggest ride-hailing and food-delivery operator, and the company behind Yandex Cloud, one of the few large-scale cloud platforms still operating inside Russia since most Western hyperscalers withdrew after 2022. According to Reuters, the first strike on October 8 was the first major attack on a Russian data hub since the start of the war.

Google · Preferred Sources

Don't miss new tech stories on Google

Add TrendinTech once in the Google app and our stories appear in your news suggestions.

Add Now

What Happened at Yandex’s Data Centers

Yandex says a drone attack caused a fire at its data center in Sasovo, in Russia’s Ryazan region, on October 8, 2026. The company said the facility’s operations were completely suspended as a result. Sasovo is one of Yandex’s five large data centers and, according to the company, hosts tens of thousands of servers. Yandex said there were no casualties at the site.

A day later, on October 9, Yandex reported a second drone attack, this time at a data center in the Kaluga region southwest of Moscow. The company said several modules at that facility were completely disabled and that customers might experience service disruptions as a result. Then, on October 11, Yandex confirmed a third incident: a reported drone attack on its Vladimir facility, east of Moscow, that again led the company to suspend operations there completely.

Three sites, three suspensions, four days. That is the shape of the story as Yandex itself has described it, and it is worth being precise about what the company has and has not said. Yandex has confirmed physical damage and operational suspensions at all three locations. It has not published a repair timetable for any of them, and it told reporters, in its own words, that predicting a return-to-service date was very difficult.

Timeline: Sasovo, Kaluga, and Vladimir

Laying the three incidents side by side makes the escalation easier to read. Each strike hit a different facility, in a different region, with a slightly different reported outcome. The table below reflects only what Yandex and named officials have confirmed through named outlets.

Date (2026)	Location	Reported Cause	Confirmed Impact
October 8	Sasovo, Ryazan region	Drone attack, fire	Operations completely suspended; no casualties reported
October 9	Kaluga region	Drone attack	Several modules completely disabled; possible service disruptions
October 11	Vladimir	Reported drone attack	Operations completely suspended; damage assessment ongoing

Pavel Malkov, the governor of the Ryazan region, added a detail to the first incident on Telegram. He said two Ukrainian drones had been shot down over the region and that “the roof of a business caught fire” in the Sasovo area, as reported by AFP. That is the only specific drone count attached to any of the three strikes in the public record so far. Yandex has not published its own count of drones involved in any of the incidents, and no outlet in this story’s sourcing has independently confirmed the total number of drones used across all three attacks.

Yandex’s Official Statements, Quoted Directly

Yandex has mostly communicated through short written statements rather than press conferences, and those statements are the most reliable record of what the company is willing to confirm. After the first strike, a Yandex spokesperson told AFP: “A drone attack caused a fire at the Yandex data centre in Sasovo, affecting part of its infrastructure.” That is a company acknowledging damage without quantifying it.

The language shifted slightly by the third incident. Describing the Vladimir facility, Yandex’s service alert said: “Operations at the data centre have been completely suspended.” The same alert, cited by AFP, read: “As a result of a UAV attack, infrastructure at the Yandex data centre in Vladimir was damaged.” Taken together, the three statements show a company confirming physical damage each time while declining to estimate cost, repair timelines, or the scale of the disruption in financial terms.

The most candid line from Yandex came after the second strike, when the company acknowledged just how central these facilities are to its business. As quoted by the BBC, Yandex said: “Our data centres are critical for the normal operation of our services, and it is very difficult to predict when they will be back online.” That is not corporate reassurance. It is an admission that the company itself does not know how long the disruption will last.

Why Yandex’s Data Centers Matter to Russia’s Cloud Economy

To understand why three data center strikes made international headlines rather than staying a local story, it helps to understand what Yandex actually is inside Russia’s economy. The company runs the country’s dominant search engine, a major ride-hailing and food-delivery network, a mapping and navigation platform used by millions of drivers, and Yandex Cloud, a cloud computing arm that businesses and government-adjacent organizations rely on for hosting, storage, and increasingly for AI workloads.

That breadth is precisely what makes a data center outage so visible. A failure at a narrow, single-purpose data center might only affect one product. A failure at a facility that hosts “tens of thousands of servers,” in Yandex’s own description of Sasovo, has the potential to ripple across search, maps, payments, and enterprise cloud tenants simultaneously, even if no single service goes fully dark.

Yandex Cloud specifically reported electricity-supply problems affecting one data center “zone” following the Sasovo incident and advised customers to shift workloads to other zones, a standard cloud-resilience move that assumes the provider has enough spare regional capacity to absorb the loss. Whether that redundancy holds up after a second and third facility are also damaged within the same week is an open question Yandex has not addressed publicly.

Impact on Yandex Cloud, Ride-Hailing, and Payment Services

Here is where the reporting gets more cautious, and deliberately so. Users reported problems with several Yandex applications following the strikes, including the company’s ride-sharing and payment apps, a detail confirmed through user reports gathered by AFP rather than a direct Yandex statement about those specific products. Yandex, for its part, said its core consumer services were not affected by the Sasovo incident specifically.

Those two claims are not necessarily contradictory. A company can say its flagship consumer services held up at a system-wide level while individual users in affected regions or served by affected server clusters experience real, localized failures. But it does mean that broad claims about “Yandex Cloud and Yandex Pay going offline” need a caveat: no outlet in this story’s sourcing has confirmed a complete, company-wide outage of either product. What is confirmed is disruption to at least one cloud zone and user-reported problems with ride-hailing and payment apps.

Yandex Service	Reported Issue	Who Confirmed It	Scope
Yandex Cloud (one zone)	Electricity-supply problems	Yandex Cloud	Single zone; customers advised to use other zones
Ride-sharing app	User-reported outages	User reports via AFP	Unconfirmed scale
Payment app	User-reported outages	User reports via AFP	Unconfirmed scale
Core consumer services (Sasovo-related)	No confirmed impact	Yandex	Company says unaffected

Who Is Behind the Strikes: What Is Confirmed and What Isn’t

This is the part of the story that deserves the most care. Russian officials and Yandex’s own statements describe the attacks as drone strikes, and Ryazan governor Pavel Malkov specifically referenced Ukrainian drones being shot down over his region. Russian state-aligned framing and much of the Western press coverage has treated these as Ukrainian strikes, consistent with the broader pattern of drone warfare across the border region.

What has not happened, at least not in the reporting gathered for this story, is an independent, on-record confirmation from Ukraine’s government or military claiming responsibility for any of the three strikes. That distinction matters. Readers should treat “Ukrainian drones hit Yandex” as the characterization used by Russian officials and reflected in most headlines, not as a confirmed Ukrainian claim of credit. Attack attribution in this conflict is frequently asymmetric: Russia names Ukraine as the source of incoming drones far more often than Ukraine confirms specific strikes, for its own operational security reasons.

Historical Context: A First-of-Its-Kind Target

The Reuters framing of the October 8 strike as the first major attack on a Russian data hub since the war began is the single most important piece of historical context here. Over the previous years of the war, drone and missile campaigns on both sides have concentrated heavily on energy infrastructure, refineries, and military-adjacent industrial sites. Civilian-facing digital infrastructure, especially privately owned tech company facilities, had largely stayed outside that target set, at least as far as major, confirmed strikes go.

That makes the Sasovo strike a notable shift, and the fact that it was followed by two more strikes on the same company within days suggests it was not an isolated, opportunistic hit. Three confirmed incidents against the same corporate entity in a single week reads less like coincidence and more like a sustained campaign, regardless of who is ultimately proven responsible. It also puts Yandex in a category previously occupied mostly by state-owned energy and defense infrastructure: a named, repeatedly targeted entity whose outages make international news within hours.

Market and Business Impact on Yandex

Yandex has not disclosed a financial estimate for the damage across any of the three sites, and nothing in the current reporting supports a specific dollar figure, so none should be assumed. What can be said with confidence is that the company is now operating with reduced capacity at three of its five large data centers simultaneously, each at a different stage of damage assessment and recovery.

For a company whose cloud division has been positioning itself as a domestic alternative to the Western hyperscalers that exited the Russian market after 2022, repeated physical attacks on its core infrastructure cut against the pitch of reliability that any cloud provider needs to sell to enterprise customers. Even if Yandex restores each site within weeks, the pattern itself, three hits in four days, raises the kind of uptime and business-continuity question that enterprise cloud customers in any market tend to ask before renewing a contract.

Competitive Comparison: Yandex Cloud’s Position Without Western Rivals

One detail that shapes how much this outage matters is who Yandex is actually competing against right now. Since 2022, Amazon Web Services, Microsoft Azure, and Google Cloud have all wound down operations inside Russia, leaving the domestic cloud market to local players such as Yandex Cloud, alongside smaller Russian providers. That absence of Western competition means Russian enterprises have fewer alternative providers to shift workloads to if Yandex’s capacity stays constrained.

In most global cloud markets, a multi-day disruption at three facilities belonging to one provider would push customers toward multi-cloud failover with a rival hyperscaler almost immediately. Inside Russia’s more closed cloud market, that option is far more limited. This is also why Yandex’s advice to its own customers, after the Sasovo incident, was to move workloads to a different Yandex Cloud zone rather than to a competing platform: the fallback has to stay inside the same company’s infrastructure, because the realistic external alternatives are scarce.

How This Differs From a Typical Hyperscaler Outage

Outages at AWS, Azure, or Google Cloud are almost always software, configuration, or power-grid failures, resolved within hours through failover and engineering fixes. What makes the Yandex situation structurally different is that the root cause, physical drone damage to buildings and server modules, cannot be patched. Rebuilding or repairing damaged modules takes physical construction and hardware replacement time that a software rollback simply does not require, which is consistent with why Yandex itself has declined to give a recovery date.

What Engineers Monitoring Third-Party Cloud Dependencies Should Watch

For engineering teams anywhere in the world who depend on a single cloud region or a single vendor’s infrastructure, this episode is a reminder that physical-world events, not just software bugs, can take out a data center zone. Teams that rely on any single cloud provider’s status page as their only signal should also track independent monitoring and news sources, since a vendor’s own dashboard can lag behind what customers are already experiencing. A simple scripted check against a provider’s public status API, run on a schedule, is a low-effort way to catch a zone-level problem before it shows up in a dashboard.

curl -s https://status.example-cloud.com/api/v2/status.json | jq '.status.indicator, .status.description'

That pattern, polling a status endpoint and alerting on any indicator change, is the same basic approach used in uptime monitoring for any cloud cost and infrastructure monitoring setup, and it applies just as well to watching for a vendor-side outage as it does to watching your own cluster. For teams already thinking in multi-cloud terms, tools built around Terraform and Kubernetes multi-cloud deployments make it easier to shift workloads between providers quickly if one region becomes unreliable, which is exactly the kind of flexibility Yandex Cloud customers currently lack.

The Broader Pattern of Infrastructure as a Target

Data centers joining the list of struck infrastructure also lands at an interesting moment for the data center industry more broadly, which has already been grappling with physical-world constraints far removed from warfare, from water-supply risk at data centers relying on produced water for cooling to the industry-wide scramble for power capacity as AI workloads grow. Yandex’s situation is a far more acute version of a broader truth the data center industry has had to confront this year: these facilities are large, fixed, physical targets, whether the threat is drought, grid strain, or in this case, military conflict.

It also arrives alongside a wider tightening of the technology relationship between the West and Russia. The European Union’s most recent sanctions package, reported to cover roughly 1,600 targets, has focused heavily on chips and drone components reaching Russia’s supply chain, as covered in TrendinTech’s earlier reporting on EU sanctions targeting Russia’s tech supply chain. Whether Yandex’s own hardware sourcing, including replacement parts for damaged server modules, is complicated by those same sanctions is an open question nobody has answered publicly yet.

Not Yandex’s First Rough Week in the Headlines

This is also not the first time in recent months that a Yandex outage has drawn scrutiny. An earlier incident this year prompted analysis of exactly how much of the reported disruption could be attributed to normal bot traffic patterns rather than a genuine failure, a story examined in detail in TrendinTech’s coverage of a prior Yandex outage and its bot-traffic data. That earlier episode is a useful contrast: it was a case where surface-level outage symptoms turned out to have a mundane explanation. The current string of drone strikes is the opposite case, a situation where Yandex itself has confirmed physical damage at three separate sites, removing any ambiguity about whether something real happened, even if the downstream consumer impact is still being sorted out.

Broader Market Ripples: AI Infrastructure Under Pressure

Yandex’s cloud and AI ambitions were already being squeezed by forces unrelated to the war. Elsewhere in the data center sector, Taiwan’s ProLogium has been shifting roughly half of its sales toward AI data center customers as its original aerospace and EV battery markets slow, a sign of just how much gravitational pull AI infrastructure now exerts on suppliers everywhere, detailed in TrendinTech’s report on ProLogium’s pivot toward AI data centers. Yandex, by contrast, is dealing with the opposite problem: infrastructure capacity being physically removed rather than added, at the exact moment regional demand for AI and cloud services is rising.

Predictions: What Happens Next

Expect Yandex to issue further short, factual service alerts rather than a single comprehensive damage report, continuing the pattern it has followed after each of the three strikes so far.
If additional Russian data centers are hit in the coming weeks, expect Russian officials to continue attributing strikes to Ukrainian drones without a matching on-record Ukrainian claim of responsibility, keeping attribution formally unconfirmed even as the pattern continues.
Enterprise customers of Yandex Cloud inside Russia are likely to press the company for clearer multi-zone redundancy commitments, given the limited realistic alternative of switching to a Western provider.
Watch for whether sanctions on chip and component exports to Russia, already a focus of the EU’s recent 1,600-target sanctions package, end up slowing Yandex’s ability to source replacement hardware for the damaged Kaluga and Vladimir modules.
If a fourth Yandex facility is struck, expect international coverage to shift from describing isolated incidents to explicitly framing this as a sustained campaign against Russian digital infrastructure, a framing that is already emerging after three hits in four days.

Frequently Asked Questions

Did Yandex Cloud go completely offline?
No. Yandex Cloud reported electricity-supply problems affecting one data center zone after the Sasovo strike and advised customers to use other zones. No outlet in the current reporting has confirmed a complete, company-wide outage of Yandex Cloud.

How many Yandex data centers have been hit?
Three, according to Yandex’s own statements: Sasovo in the Ryazan region on October 8, 2026, a facility in the Kaluga region on October 9, 2026, and a facility in Vladimir on October 11, 2026.

Was anyone hurt in the attacks?
Yandex said there were no casualties at the Sasovo facility. The company has not issued a separate casualty statement for the Kaluga or Vladimir incidents in the reporting reviewed for this story.

Has Ukraine claimed responsibility for the strikes?
Not on the record, based on current reporting. Russian officials, including Ryazan governor Pavel Malkov, have described the incidents as involving Ukrainian drones, but no independently confirmed Ukrainian government or military statement claiming responsibility appears in the sourcing for this story.

Were Yandex’s ride-hailing and payment apps affected?
Users reported problems with several Yandex applications, including its ride-sharing and payment apps, following the strikes. Yandex has said its core consumer services were not affected by the Sasovo incident specifically, so the scale of impact on those particular apps remains unconfirmed.

How many of Yandex’s data centers are there in total?
Yandex has described Sasovo as one of its five large data centers. The company has not published a public map or full list of all five sites’ names and locations in the statements reviewed here.

When will the damaged facilities be back online?
Yandex has not given a timetable for any of the three sites. The company said directly that it is very difficult to predict when its data centers will be back online.

Is this the first time a Russian data center has been attacked in the war?
According to Reuters, the October 8 Sasovo strike was the first major attack on a Russian data hub since the start of the war with Ukraine, making the subsequent Kaluga and Vladimir strikes part of an unusually concentrated, first-of-its-kind pattern against the same company.

Yandex Drone Strikes: 3 Data Centers Hit in 4 Days [2026]