Yandex Data Center Attacks Trigger Outages, Cloud Disruptions and Stock Decline
A series of physical attacks has led to the complete or partial shutdown of several key Yandex data centers. In the night of 8 October a fire broke out at the facility in Sasovo, Ryazan region. On 9 October multiple modules at the Kaluga site failed completely, and on 11 October the entire Vladimir data center was taken offline.
The outages have already caused Yandex shares to lose almost 9 percent of their value over five trading sessions, with the stock briefly touching 3,255 rubles. Investors are now pricing in both direct restoration costs and the long-term expense of hardening physical security across the infrastructure.
Scale of the Damage and Recovery Outlook
Analyst Dmitry Lozovoy of Finam stated that the incidents affected not only cloud infrastructure but also a range of consumer services. Recovery is taking longer than initially expected because of the scale of physical damage and limitations in existing redundancy systems. Independent analyst Pavel Shumilov highlighted that three of the five main data centers have now been hit and warned that further strikes on the remaining sites, including Mytishchi, cannot be ruled out.
Oleg Abelev of Rikom-Trust pointed out that the Sasovo facility housed two of the company’s three supercomputers. Its loss would significantly slow the training of new neural-network models. Restoration of power and cooling systems may take weeks, while replacement of damaged server modules and supercomputers could require up to two years given global chip shortages.
Financial and Operational Consequences
Although Yandex Cloud accounts for less than 2 percent of total IFRS revenue, the attacks are expected to drive higher capital expenditure. Companies may face increased equipment prices of two to three times current levels, potential client migration to competitors and the need to add new clauses covering force-majeure events in service agreements.
Analysts from Vector Capital noted that moving capacity to the existing site in Karaganda, Kazakhstan, is complicated by sanctions risks and insufficient spare capacity. Natalia Milchakova of Freedom Global lowered the rating on Yandex shares from “Buy” to “Hold” while keeping a 5,000-ruble target price, citing the new persistent infrastructure risk.
Market Reaction and Investor Outlook
Most analysts agree that short-term pressure on the stock will continue. However, some see limited downside because shares have already fallen 25 percent since the start of 2026 and currently trade at multi-year valuation lows relative to growing revenue and profit. Support levels are identified around 3,100–3,200 rubles, with a potential rebound toward 3,700–4,000 rubles if attacks cease and positive geopolitical signals emerge.
Related articles
Cyber Attack on Danfoss Systems Forces Defrost in 250 French Supermarkets, Spoiling Stock
Hackers compromised refrigeration control systems supplied by Danfoss in French supermarket chains Intermarché and Coopérative U, activating continuous defrost cycles that raised temperatures to 50 °C. The sabotage affected between 150 and 200 Intermarché stores and nearly 100 Coopérative U locations, forcing retailers to discard large quantities of fresh and frozen goods. French authorities confirmed the incidents, with the Paris prosecutor’s office opening an investigation after reports of associated fires. The attackers exploited the normal maintenance function of the Danfoss equipment, turning brief defrost cycles into prolonged warming that broke the cold chain. Coopérative U chairman Dominique Schelcher described the event as unprecedented and stated that technical teams are working with refrigeration specialists to restore operations. No group has claimed responsibility, and investigators continue to examine the initial access vector. The incident illustrates how manipulation of industrial control systems can produce immediate physical and financial damage without traditional data theft or encryption.
Yandex Cloud Cascade Failure October 2026 Exposes Multi-AZ Limits and Capacity Exhaustion Risks
In October 2026, Yandex Cloud suffered a prolonged cascade outage across multiple data centers in Sасово, Калуга, and Владимир, triggered by power failures and a drone-related fire that fully disabled the ru-central1-b zone. The incident revealed that standard Multi-AZ designs reach physical capacity exhaustion when multiple zones fail simultaneously, leaving insufficient resources in remaining zones for automatic failover. Businesses relying on managed Kubernetes, databases, and SaaS platforms such as Salebot and CIAN experienced extended recovery times, with backups becoming inaccessible and RTO stretching beyond 24 hours due to index rebuilds and manual quota allocation. Yandex Cloud responded by manually distributing quotas, partnering with Selectel, K2Cloud, and VK Cloud for emergency capacity, and advising clients to activate external disaster recovery plans. The outage also highlighted single points of failure in DDoS protection configurations and Control Plane dependencies that prevented timely migration of master nodes. Architectural recommendations include deploying independent edge webhook buffers using FastAPI on separate VDS instances to preserve incoming events during primary backend failures. Overall, the events underscore the necessity of true multi-cloud strategies that avoid reliance on any single provider's IAM, billing, and physical infrastructure.
Passkeys in Production: How One Developer Replaced Passwords with Face ID in Three Days Using FastAPI and Next.js
Yaroslav Morozov details a complete production implementation of Passkeys based on the WebAuthn standard and FIDO2 protocols. The article explains why Passkeys eliminate phishing and database breach risks compared to traditional passwords while providing biometric login via Face ID or Touch ID. It covers database schema design with PostgreSQL tables for credentials and challenges, SQLAlchemy models, and minimal dependencies including py-webauthn on the backend and SimpleWebAuthn on the frontend. Full working code for registration and authentication flows is provided, showing how Passkeys integrate with existing JWT token systems without major refactoring. The guide includes environment configuration, error handling, challenge management with five-minute TTL, and security considerations such as sign count verification to detect cloned keys.
Yandex Disk Files Become Partially Inaccessible After Sasovo Data Center Incident
A detailed user report reveals that approximately one percent of files stored on Yandex Disk are currently unavailable for download following reported incidents at the Sasovo data center. The problems manifest in three distinct states: missing thumbnails with downloadable originals, visible thumbnails with inaccessible originals returning 504 Gateway Time-out errors, and cases where both thumbnails and originals fail to load. Technical analysis using curl requests traced the failures to specific storage nodes such as s418klg.storage.yandex.net, indicating that some data shards may reside in affected infrastructure while others remain operational. Yandex support requested original files for diagnosis but closed the ticket without providing an official explanation or confirming data integrity. The author emphasizes that the issue affects files across both the Photos and Files sections and recommends maintaining offline backups due to the lack of guaranteed availability during data center failures.