Kremlin Confirms Yandex Crisis Talks 2026: What Happened

On October 13, 2026, Kremlin spokesman Dmitry Peskov said the government was discussing problems at Yandex after attacks on its data centers. The outages followed attacks on Russian data-center infrastructure, raising concerns for customers, businesses, and public agencies that rely on those services.

An availability zone is a separate cloud infrastructure location that can keep services running independently of another zone. A government discussion does not confirm a formal crisis meeting, a recovery timetable, or a plan to repay users. The disruptions come amid the wider war between Russia and Ukraine, where attacks on infrastructure have also affected technology operations. For customers, the immediate question is whether affected services will return, while the Kremlin has not announced a compensation plan.

Key Takeaways

• Peskov confirmed a government discussion of Yandex’s problems.
• He said it was too early to assess user financial losses.
• Three Yandex data centers were attacked within a week.
• Outages affected cloud services, apps, and organizations that depend on Yandex.
• Yandex users have not received a Kremlin compensation promise.
• Decree No. 604 allows temporary state management under stated conditions.

What did the Kremlin say? Kremlin confirms yandex crisis talks 2026

Peskov confirmed that the government was discussing Yandex’s difficulties, while saying it was too early to assess users’ financial losses. His statement confirmed a government discussion, not a detailed crisis meeting or a decision to repay customers. He also said Yandex was taking urgent steps to address the consequences.

The Kremlin has announced no compensation mechanism for affected users. Peskov’s remarks do not show that every user suffered a financial loss, or that the government will assess individual claims. A disrupted app or cloud tool can cause trouble without creating a direct money loss.

A government discussion is not a promise to compensate customers, and it does not set a recovery deadline.

That distinction matters because Yandex serves both individual users and organizations. A business that could not reach a cloud service may have faced costs, while another customer may have noticed only a short delay. The government has not described how it would measure those different effects.

Yandex’s urgent response points to work on restoring service, but it does not establish when every function will return. In a cloud platform, recovery can happen in stages as systems and customer access come back online. Some features may work before a full service has returned.

The company’s problems are therefore both an operations issue and a customer concern. Users may want to know whether a payment, account, or stored file remains safe. Peskov’s comments did not settle those individual questions, and they did not announce a separate claims process.

The word “talks” can suggest a formal meeting, but Peskov’s statement only confirmed that officials were discussing the matter. No agenda, participants, or meeting date were announced. That leaves the government’s role less defined than the company’s immediate work to limit disruption.

Readers should separate the government’s attention from any remedy for customers. A discussion can lead to further action, but no specific step can be assumed from Peskov’s comments alone. Treat the statement as confirmation of government discussion, not as a commitment to compensate customers.

Which Yandex data centers were hit, and what was damaged?

Three Yandex facilities were hit within a week, but the reported impact differed by site. Sasovo shut down after serious damage, Kaluga lost part of its infrastructure, and Vladimir suspended operations. The attacks raised questions about damage to Yandex data and the company’s ability to keep services running.

Yandex operated five data centers, and two of its three neural-network-training supercomputers were at Sasovo. The table shows the distinct reported effects at each facility.

Sasovo and Kaluga

Yandex said a drone attack on the night of October 7 to 8 seriously damaged its Sasovo data center in Ryazan region. Fire damage shut down the site. The loss mattered beyond the building because two of the company’s three supercomputers used for neural-network training were there.

On the morning of October 9, an attack on Yandex’s Kaluga data center left part of its infrastructure out of service. Fire Point said Ukrainian forces struck the 63-megawatt facility. The group described it as Yandex’s largest of five data centers and the second Yandex site targeted.

A Help Net Security report on the attacks also described Sasovo as seriously damaged and shut down. The site-level differences matter: a full shutdown has a different effect from an outage affecting only part of a facility.

The Vladimir facility

The Vladimir data center was damaged on October 11, and its operations were completely suspended. Its impact added another disruption while the earlier sites remained part of Yandex’s recovery work. The three strikes did not produce the same operational result.

Yandex reported no employee injuries at Sasovo or Kaluga, and no one was injured at the Vladimir facility.

Which services and users experienced disruption?

The impact ranged from unavailable cloud tools to interrupted daily tasks such as paying, ordering a ride, and checking records. Yandex services and users saw different effects, depending on the platform and location. Some disruption lasted for days, while other problems appeared as temporary access failures.

From October 8-11, Yandex Cloud connectivity fell to around 30% of normal, affecting 84 cloud services. The figures show how a data-center problem can reach both direct customers and organizations using the platform behind the scenes.

Cloud access and Yandex accounts

Early on October 10, the ru-central1-b availability zone remained unavailable, and 32 cloud services were listed as unavailable. Yandex Cloud’s other availability zones were working. That left some customers with access to the platform but not every service they used.

Yandex Pay was partly available on Monday and showed a message reassuring customers that their money was safe. A Moscow Times reporter could not access the full Yandex Taxi ride history on Monday. These examples show that app access and stored account details are separate concerns.

A TASS report on service recovery said Search, Alisa, Mail, Maps, and Taxi were gradually recovering, though some functions remained unavailable. Yandex said customer account records were not affected. The company also arranged temporary data and service capacity with VK Cloud, Selectel, and K2Cloud.

Apps and outside organizations

Yandex Go was temporarily unavailable in Tbilisi, while a doctoral student in New Zealand could not use Yandex Archives. Dozens of court hearings across Russia were disrupted. The effects reached people who did not use a consumer app for daily errands.

Maps, car-sharing, food delivery, email, banking, and streaming also faced disruption. Reports described problems with dating apps, residential access systems, smart homes, Kaluga-region government websites, and the FIT&ZEN fitness app and website. These services show how one provider’s infrastructure can sit behind many different tasks.

When a cloud service connects to another company’s app, the user may not know which provider caused the delay. The visible problem might appear in a payment screen, a court system, or a building door. For a small business or public agency that relies on one cloud zone, an outage can interrupt its own service even when its customers never use Yandex directly.

Why could data-center outages affect services across Russia?

A failure at one large provider can reach businesses and public services because their systems may depend on the same cloud infrastructure. Russia has more than 200 data centers, hundreds of telecom network nodes, and corporate server rooms. Yet commercial capacity is concentrated in Moscow and nearby regions.

Russia’s internet is a large network, not one system that can be switched off by striking data centers. Still, shared infrastructure can spread an outage across customers that rely on the same provider or location.

Concentrated infrastructure and dependencies

Yandex, VK, Rostelecom, and Sberbank are among Russia’s major data-center owners. A large provider may host services used by other companies, so a cloud failure can reach a public agency or small business through its own software. The customer may not have a direct relationship with the data-center operator.

Data localization rules require covered data to stay within Russia. Rules also affect hosting, authentication services, and critical information infrastructure. These limits can narrow a company’s options for moving data abroad when a local facility fails.

Russia gets almost all necessary equipment through parallel imports, which means goods enter through routes outside the original maker’s direct sales channel. Replacing servers and other equipment may take time. The AI boom has also driven up equipment prices, adding pressure to a strained market.

The system has many parts, so attacks on a few sites do not mean the whole internet will stop. But concentrated commercial capacity and links between services can make local damage felt far beyond one building. Cloud customers need plans for the systems that depend on a provider.

Practical ways to limit outage exposure

Businesses can lower the risk that one damaged site will interrupt all their work. These steps help teams prepare for a service failure without assuming that every system can move freely across borders.

• Keep backups in a separate availability zone.
• Maintain a copy in a separate region where permitted.
• Test restoration and failover, the switch to a backup system.
• Prepare outage messages for customers and staff.

A backup only helps if the business can restore its data and reach the people who need it. Separate zones can still depend on shared systems, so teams should know what each backup covers. Regular damage would strain replacement capacity further because equipment depends on parallel imports and AI demand has raised prices.

What does Decree No. 604 allow the government to do?

Decree No. 604 creates a conditional route for temporary state management of business property, tied to failures to secure or restore critical facilities. Russia signed the decree in August 2026. Its power is conditional, and the decree’s existence alone does not show that officials used it against Yandex.

The stated trigger is a business’s failure to secure or restore a critical facility. The decree sets out a government option, not proof of action against a particular company. The distinction matters as officials discuss infrastructure problems after the attacks.

Conditions for temporary state management

The decree allows the government to place business property under temporary state management if a business fails to secure or restore critical facilities. The condition ties the power to a facility’s protection or recovery. It does not make state management automatic after an attack or an outage.

Readers can track four decision points as the government responds to infrastructure incidents:

• Whether authorities identify a critical facility.
• Whether a business is found to have failed to secure it.
• Whether the business fails to restore it.
• Whether the government announces temporary management of property.

Each point matters because the stated power depends on both the facility and the business’s actions. An attack by itself does not establish that a company failed to protect or restore a site. A formal government announcement would provide evidence of temporary management.

Who the decree can cover

The decree’s scope includes covered business property and certain entities tied to Russian legal entities. That wording reaches beyond a company’s direct local owners. The legal definition matters when control sits outside Russia.

A legal power is not evidence that the government has used it against a specific company.

The decree identifies foreign controlling persons of Russian legal entities among the covered entities. That does not mean every foreign investor or overseas business automatically falls within its reach. The stated scope depends on the entity’s relationship to a Russian legal entity.

Readers should distinguish the decree’s legal scope from a government decision about one company. No announcement described in this account says officials placed Yandex property under temporary state management. Its stated scope includes foreign controlling persons of Russian legal entities, so ownership structure is part of the decree’s reach.

Conclusion

The Kremlin has confirmed that Yandex’s problems are under government discussion, but that is not the same as a recovery timetable or compensation promise. The situation is an infrastructure and continuity problem as well as a customer-service issue. Its effects can reach businesses and public services that depend on cloud tools.

Affected users and businesses should check Yandex service-status updates before relying on a disrupted tool. Keeping an alternative payment or access option available can help during an outage. Readers who want more technology and news updates can choose topics through the Occcy newsletter. Customers and dependent businesses can reduce immediate uncertainty by checking service status and keeping a workable backup option.