In Part 1, we established what happened: Ukrainian drones struck three Yandex data centers in four days, then hit Sberbank’s under-construction mega-center, shutting down everything from taxis to digital payments. That’s the story of the strikes.
This part is about the damage — the people and businesses who turned out to have built their operations on top of one company’s servers, and what happened when those servers disappeared.
The one point of failure
The single most useful framing for this event came from a security analyst, who put it bluntly to Newsweek:
“When you hit a single point of failure like Yandex that provides services to thousands of businesses in a network or supply chain, you can cause outages throughout the network and damage to the whole supply chain.”[^1]
Yandex isn’t just an app you open. It’s infrastructure: a payments rail, a cloud provider, a logistics platform, and an e-commerce marketplace wrapped in one company. That concentration is convenient when things work — and catastrophic when the buildings that hold it all start burning.
Banking, payments, and the money problem
The most immediate and frightening impact was financial, and it came in two waves.
First, Yandex Pay — the digital wallet that effectively replaced Apple Pay in Russia after Western payment rails left — went down with the Vladimir data center. Users couldn’t check balances, pay for purchases, or transfer money. Yandex’s own fintech chief, Dima Pirogov, issued the digital-age version of a bank-run reassurance: “All your money is safe. The money itself isn’t stored in the data center.”[^2]
True or not, that reassurance didn’t stop the panic. A Moscow woman saving for a car found 1.5 million rubles (~$17,830) simply absent from her Yandex Pay balance and, in her words, “cried my eyes out.”[^3] Yandex scrambled to contain the trust damage: it waived all Yandex Cloud and Yandex 360 fees for October 8–31, waived Yandex Pay late fees and interest incurred during the outage, and raised savings-account rates to 20% that week[^4].
Second came Sberbank. On October 14, drones struck the bank’s data center in Balakovo — a 122.2-billion-ruble (~$1.4 billion) project intended to become one of Europe’s largest, and to host Russia’s biggest supercomputer plus parts of the state’s “GosTech” platform[^5].
Here’s the tell: Sberbank’s deputy chairman insisted “all banking systems and online services continued to operate normally,” even as independent outage trackers logged user complaints against Sberbank itself, its GigaChat AI chatbot, its Samokat grocery-delivery service, plus Tochka Bank, Alfa-Bank, VTB, and Rosselkhozbank[^6]. That gap between “operating normally” and what thousands of users actually experienced is its own story — one we’ll keep returning to, because it matters for anyone trying to trust an official timeline.
Retail, e-commerce, and logistics: the screen and the warehouse
This is where the impact stops being a tech story and becomes a supply-chain story.
When the data centers fell, the disruptions rippled out to companies that had nothing to do with the war — they’d just bought cloud services from Yandex. Grocery giant Magnit, fast-food chain Vkusno i Tochka, appliance retailer M.Video, fashion retailer Lamoda, pizza chain Dodo Pizza, flower seller Flowwow, fitness app DDX, and car-sharing service Delimobil all reported outages[^7].
The most revealing single datapoint came from Yandex Market (the company’s Amazon equivalent). In a candid service update, it reported that its sorting centers were temporarily unavailable — but its pickup points and warehouses were operating normally[^8]. That sentence matters more than it looks: it’s the moment the outage jumped from “websites are down” to “packages aren’t moving.” The cloud isn’t just pixels — it’s the software that routes physical goods.
And this wasn’t confined to Yandex’s own cloud. Since mid-July, Ukrainian drones had already been striking the warehouses of Wildberries and Ozon, Russia’s two largest online retailers, forcing them to redistribute inventory and reroute shipments[^9]. By mid-October, even Vladimir Putin was admitting — unusually — that Russia’s security services had “failed to anticipate attacks targeting commercial logistics hubs like Wildberries and Ozon.”[^10]
A scope note, in the interest of accuracy: the causal evidence directly tying the data-center strikes to maritime shipping, freight rail, or commodity-trading systems is thin in English-language reporting so far. What we can document is the last-mile and first-mile logistics layer — fulfillment, sorting, delivery, and urban mobility — plus a measurable shock to the hardware that logistics runs on (more on that below). It would be wrong to claim the strikes sank a cargo fleet; it would be just as wrong to call this only a “website” story.
The gig economy and the small business
The people who felt it hardest weren’t executives — they were the workers whose entire income ran through Yandex’s apps.
Taxi drivers described what one called “phantom orders”: the system dispataching four different cars to the same passenger, and — worse — drivers being unable to withdraw the money they’d earned, making it impossible to pay for fuel and car rentals. One driver told CNN he had to return his rental car because he couldn’t afford to keep paying for it while not earning. “For many drivers,” he said, “this isn’t just a technical glitch — it’s a question of whether they can continue working and supporting themselves.”[^3] At one point, Yandex was reportedly telling drivers to switch to Google Maps or Waze while it fixed its own navigation[^11].
Small businesses absorbed an invisible hit. A travel-agency founder believed she’d lost a website she’d spent ten years building, along with its databases, photos, and reviews[^12]. Yandex Disk users reported being locked out of their own files — downloads returning HTTP 302/500/504 errors — with the company refusing, for days, to say whether any stored data had been irreversibly lost[^13]. One SaaS company, the chatbot builder Salebot, ran its servers in Yandex Cloud and was knocked offline with no say in the matter[^14].
Then there was the second-order market shock that almost no early coverage caught: the price of servers and data-processing equipment in Russia jumped 10–15% in the days after the strikes, as thousands of fleeing Yandex Cloud customers simultaneously raced to rent capacity from competitors[^15]. A catastrophe for one company became an unexpected windfall — and a capacity crunch — for its rivals.
The neighbors: this wasn’t just a Russia problem
One of the least-reported facts of the first week is that Yandex’s outages hit eight or more countries, not one.
Users in Kazakhstan, Kyrgyzstan, Uzbekistan, Armenia, Serbia, and Belarus all reported losing Yandex Go taxi service, food delivery, and Yandex Pay[^16]. In Kazakhstan, Yandex Go was reportedly down for 36 hours in some areas, and the government’s Ministry of Artificial Intelligence and Digital Development had to step in to help coordinate recovery[^17]. In Kyrgyzstan, the outage became a parliamentary talking point — one MP argued the country needed its own digital platforms rather than depending on a foreign app for its gig economy[^16].
The uncomfortable lesson for the region: many of these countries store their citizens’ data locally, by law — but the applications still ran on servers in Moscow. Local servers didn’t mean local resilience[^16]. Digital dependence, it turns out, doesn’t respect borders.
The knock-on effects no one planned for
Finally, a short list of consequences that caught even close watchers by surprise:
The courts stopped working properly. Russia’s “Moy Arbitr” electronic case-filing system — which runs through a company called PravoTech, hosted on Yandex Cloud — suffered a “mass outage,” forcing the postponement of dozens of arbitration-court hearings across multiple regions from October 8 onward[^18].
Travel agencies couldn’t issue documents. Russia’s association of tour operators warned that clients faced delays in vouchers and tickets because booking systems depended on Yandex services[^8].
Customers started leaving — structurally, not just temporarily. Yandex struck emergency deals with rival cloud providers Selectel, K2Cloud, and VK Cloud to accelerate migration of affected corporate clients, and some companies began moving off the platform for good[^19]. One developer wrote on Habr, Russia’s technical forum, that they were replacing Yandex Metrika analytics with a competitor so “the data stays with us.”[^20]
Even the legal paperwork changed. Yandex quietly added a force-majeure clause to its user agreement — explicitly covering drone and missile attacks — meaning that, going forward, the company has legally pre-empted liability for exactly this kind of disruption[^21].
The through-line
Put it all together and a clear picture emerges: the concentration that made Yandex efficient is the same concentration that made it catastrophic to lose. Banks, delivery workers, courts, travel agencies, small retailers, and neighboring-country gig economies all turned out to be standing on the same handful of buildings.
The market put a round number on it: 77 billion rubles (~$918.5 million) wiped off Yandex’s value in two days[^4]. But that only measures what shareholders lost. It doesn’t capture the taxi driver who returned his car, or the small business owner who couldn’t recover a decade of work.
In Part 3, we’ll get technical: how you physically secure a data center against drones, how long recovery actually takes (spoiler: some of it is years, not weeks), and what this precedent means for the trillion-dollar global data-center industry that most of us didn’t realize we depend on.
Sources
[^1]: Newsweek, “Could Ukraine strikes on Russian data center impact bots? What we know,” (Oct. 13, 2026). Link
[^2]: The Register, “Ukrainian drone strikes on Yandex datacenters knock cloud and payments offline,” (Oct. 12, 2026). Link
[^3]: CNN, “Ukraine targets Russia’s ‘Google’ as the internet becomes a new front line,” (Oct. 17, 2026). Link
[^4]: The Moscow Times, “Yandex Waives Cloud and Software Fees After Ukrainian Drone Attacks on Data Centers,” (Oct. 13, 2026). Link
[^5]: The Moscow Times, “Ukrainian Drones Hit Sberbank Data Center After Yandex Attacks,” (Oct. 14, 2026); POLITICO, “Ukrainian drones strike data center of Russia’s biggest bank,” (Oct. 14, 2026). Link
[^6]: UA.NEWS, “A large-scale internet outage occurred in Russia following a drone attack on Sberbank’s data center,” (Oct. 14, 2026); Militarnyi, “Russian Banks and Online Services Experience Widespread Outages After Strike on Sberbank Data Center,” (Oct. 14, 2026). Link
[^7]: vc.ru, “Дата-центр «Яндекса» во Владимире остановил работу после атаки беспилотников,” (Oct. 11, 2026); The Moscow Times, “Ukraine’s Strikes on Yandex Data Centers, Explained,” (Oct. 12, 2026). Link
[^8]: vc.ru, “Дата-центр «Яндекса» во Владимире остановил работу…,” (Oct. 11, 2026). Link
[^9]: Anadolu Agency, “Russia’s digital economy faces a new front as Ukrainian drone strikes hit critical tech facilities,” (Oct. 16, 2026). Link
[^10]: The Moscow Times, “Putin Vows Retribution for Attacks on Russian Data Centers While Downplaying Damage to Refineries,” (Oct. 16, 2026). Link
[^11]: UNITED24 Media, “Russia’s Yandex Taxi Gets Knocked Offline and Turns to Google Maps for Help,” (Oct. 12, 2026). Link
[^12]: The Independent, “Broken dating apps and delayed takeaways: How Ukrainian strikes on data centres are upending daily life in Russia,” (Oct. 15, 2026). Link
[^13]: BleepingComputer, “Yandex confirms service outage as users lose access to cloud files,” (Oct. 12, 2026). Link
[^14]: Habr, “Каскадный сбой Yandex Cloud: анатомия событий октября 2026 и выживание бизнеса вне одного облака,” (Oct. 12, 2026). Link
[^15]: RFE/RL, “How Ukraine’s Strikes On Data Centers Disrupted Taxis, Shopping, And Business In Russia And Beyond,” (Oct. 13, 2026). Link
[^16]: The Times of Central Asia, “Drone Strikes on Russian Data Centers Disrupt Yandex Services Across Central Asia,” (Oct. 12, 2026); The Diplomat, “What the Ukrainian Strikes on Yandex Tell Us About Central Asia’s Digital Infrastructure,” (Oct. 14, 2026). Link
[^17]: The Atlantic Council, “Ukrainian drone strikes highlight the vulnerability of Russia’s data centers,” (Oct. 16, 2026). Link
[^18]: Meduza, “Ukrainian strikes on Yandex data centers disrupted Russian court operations,” (Oct. 16, 2026). Link
[^19]: Data Center Dynamics, “Sberbank data center in Russia struck by Ukrainian military,” (Oct. 14, 2026); Habr, “Yandex Cloud работает в аварийном режиме после атак на три дата-центра Яндекса,” (Oct. 12, 2026). Link
[^20]: Habr (Comment by “budaevv” on the post), (Oct. 15, 2026). Link
[^21]: Habr, “Yandex Cloud работает в аварийном режиме после атак на три дата-центра Яндекса,” (Oct. 12, 2026) (Note: Force-majeure clause added Oct. 10, 2026). Link
One thought on “Part 2 – Who Actually Pays: When the Cloud Goes Up in Flames”