From Banking to Taxis, Ukraine’s Data Center Strikes Disrupt Everyday Life in Russia

Ukrainian strikes in October disrupted Russia’s digital infrastructure by damaging Yandex facilities and later hitting a VK data center in St. Petersburg. The outages mattered because both companies support services used in ordinary routines, not just specialized technology.

Yandex confirmed serious damage at one data center, the shutdown of another, and infrastructure problems at a third. Users reported failures across Yandex Pay, Yandex Taxi, Yandex Go, food delivery, maps, email, streaming, car-sharing, and dating apps. Residential access systems and smart homes also depended on Yandex infrastructure. VKontakte users later reported that photos failed to load.

The impact was uneven. Some services switched to limited functionality, while others took several days to recover. Yandex Pay remained only partly available on Monday, and a Moscow Times reporter still could not access a complete Yandex Taxi ride history. Yandex said full restoration could take much longer.

A data center is a facility containing the computers, storage systems, and network equipment that run digital services. Companies place applications and data there so users can access them through phones and computers. This matters because the visible app is often only the front end; the essential processing happens inside these facilities.

A banking app may use a data center to verify payments and display balances. A taxi app may use it to match riders, drivers, maps, and fares. Streaming platforms use similar systems to authenticate users and deliver content. Yandex infrastructure supported services ranging from payments and taxis to email, maps, food delivery, and music.

The article shows why a facility problem can spread widely. Yandex confirmed damage to one center, another shutdown, and disruptions at a third. Connectivity to Yandex Cloud fell to around 30% of normal levels, affecting 84 cloud services. Recovery depended on switching applications or infrastructure elsewhere.

The disruption was large but unevenly measured. NetBlocks reported that connectivity to Yandex Cloud fell to around 30% of normal levels after strikes from Oct. 8-11. That decline affected 84 cloud services, showing that the problem reached far beyond one consumer application.

Yandex confirmed serious damage to one data center, the shutdown of another, and infrastructure disruptions at a third. The article also says all three Yandex supercomputers were likely severely affected. A later strike hit a VK data center in St. Petersburg, where users reported problems on VKontakte, including photos failing to load.

The article does not provide a numerical count of companies relying on Yandex. It names affected or dependent services such as dating apps, residential access systems, smart homes, taxis, food delivery, maps, email, banking, and streaming. Thus, the documented scale includes 84 cloud services and many service categories, but not a total company count.

Digital services can look unrelated to users while depending on the same cloud platform underneath. If that shared infrastructure stores data, runs applications, or handles connections, damage there can interrupt many businesses at once. This made the Yandex strikes broader than a single app outage.

The article gives several examples. Yandex Pay had login and payment problems, while Yandex Taxi users lost access to some ride history. Yandex infrastructure also supported dating apps, residential-complex access systems, smart homes, maps, food delivery, email, and streaming. Yandex Cloud connectivity fell to around 30% of normal levels, affecting 84 cloud services.

Yandex employees tried to reduce the damage by switching some applications to limited functionality. Other services needed several days to recover, and the company warned that full restoration could take much longer. The incident showed how concentration around one provider can turn infrastructure damage into simultaneous failures across unrelated-looking services.

For ordinary users, the outages disrupted payments, transport, research, and daily routines. Some problems lasted days, although access was restored for certain people. The broader significance was personal: one user said the outage reminded him that the war’s consequences were moving closer to home.

Robert, a St. Petersburg barista, used Yandex Pay as his main bank account for salary and transfers. Yekaterina found Yandex Go temporarily unavailable in Tbilisi, while Nikolai could not use Yandex Archives for dissertation research. The article also mentions disruptions affecting government agencies, but the supplied excerpt ends before explaining the reported court-hearing impact.

The excerpt does not give specific examples of small-business losses or quantify economic damage. It says the immediate disruption was manageable for many users, while longer-term consequences remained unclear. Services recovered at different speeds, and Yandex warned that complete restoration could take much longer.

The article portrays Yandex as a major digital backbone in Russia. Its infrastructure supported payments, taxis, maps, food delivery, email, streaming, dating apps, residential access systems, and smart homes. Yandex Cloud alone included 84 affected services. That breadth made Yandex’s disruption important to everyday life and to organizations using its products.

The mechanism was shared infrastructure. When strikes damaged one Yandex data center, shut down another, and disrupted a third, applications built on that platform lost access or had to reduce functionality. The article also says all three Yandex supercomputers were likely severely affected, potentially setting Russia back in artificial intelligence research.

However, the provided article does not mention restrictions on foreign cloud providers. Therefore, it does not establish that such restrictions increased reliance on Yandex. It does show that Yandex had become deeply embedded in services used by people, agencies, and private firms, while future recovery remained uncertain.

Cloud computing lets a service use shared computing, storage, and network capacity instead of relying on one local machine. Backups preserve copies of data, while redundant data centers provide alternative places to run applications. Together, these safeguards can let a service continue when one facility is damaged.

Normally, traffic can be redirected to another functioning location, and applications can run with reduced features if full capacity is unavailable. Data copies can help restore accounts and records. The article says Yandex had prepared for data center outages before the strikes. Employees switched some applications to limited functionality and mitigated certain effects quickly.

Those protections were not enough to prevent broad disruption. One center was seriously damaged, another was shut down, and a third suffered infrastructure problems. Yandex’s analyst said the scale was far more serious than expected. Some services recovered within days, but full restoration could take much longer.