Habr•October 12, 2026•🇷🇺Translated from Russian

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

Habr•Other

AmneziaWG Container for MikroTik Routers Delivers Top Performance Six Months After Launch

A developer released an AmneziaWG container for MikroTik devices in February 2026 and has since added major improvements in speed, protocol support, and stability. The lightweight container leverages the router's native WireGuard implementation for cryptography while handling AmneziaWG obfuscation in software. Performance now reaches 250-350 Mbit/s on models such as Hap Ax3 and RB5009B after switching to C code and increasing buffer sizes with RouterOS 7.24. New features include server mode for connecting multiple MikroTik devices, random port hopping, IPv6 support, dynamic DNS, and offline configuration. The project survived an early GitHub ban caused by test scripts and has grown to over 370 stars while remaining fully offline and privacy-focused.

Habr•Other

Building Resilient DoH Failover on MikroTik RouterOS to Handle Unreachable Cloudflare Responses

A network administrator encountered a persistent issue in a branch office where pages like Tailwind CSS CDN failed to load despite valid DNS responses from Cloudflare DoH. The problem stemmed from unreachable IP addresses such as 8.6.112.0 and 8.47.69.0 returned by the resolver, which RouterOS treated as healthy because it only checked for valid IP types rather than route reachability. RouterOS supports only a single active DoH upstream via the use-doh-server parameter, requiring custom scripting for failover between multiple endpoints like Cloudflare and dns.google. The solution involved static DNS entries for bootstrap addresses, certificate trust anchors including SSL.com TLS ECC Root CA 2022, and a health monitor script that probes using DNS-JSON API calls instead of switching the resolver directly. Multiple iterations addressed issues like cache-based false positives, plain DNS fallback risks from provider spoofing, and clock validation to prevent certificate failures. The final implementation uses thresholds for failure and recovery to avoid flapping and ensures post-switch verification before committing to a backup endpoint.

Habr•Other

NetRuleRouter Alpha Released to Route Traffic Across Multiple Connections Without Disabling VPN

Developer krox1 has released the first public alpha of NetRuleRouter v0.1.0-alpha.1 for Windows and Linux, a local network policy manager that distributes traffic between primary and secondary connections based on domains, IP ranges, applications, and subnets. The tool emerged from practical issues that intensified after Russian authorities discussed VPN restrictions in March 2026, with operators and platforms later prompting users to disable VPN for domestic services. NetRuleRouter sits on top of existing connections rather than acting as a VPN client or proxy, allowing users to keep corporate VPNs, personal VPNs, and direct internet active simultaneously. It supports seven matching methods including exact domains, wildcard subdomains, CIDR ranges, and application paths, with priority rules to resolve overlaps and built-in leak protection that prevents protected destinations from falling back when the secondary connection drops. The alpha includes diagnostic tracing, preset rule sets for Russia and other regions, import/export capabilities, and a first-run wizard that configures the background service and initial bindings. Limitations around DNS, shared IPs, and brief startup windows are documented, and the project explicitly does not protect against account-level blocks by services such as Anthropic.

Habr•Other

Setting Up Nextcloud Talk on TrueNAS with Custom Domain for Private Family Calls

A detailed guide explains how to deploy Nextcloud Talk on a TrueNAS server behind a custom domain to create a self-hosted messaging and calling platform for family use. The author addresses problems with commercial messengers such as VK notifications failing on iOS and Telegram requiring VPN connections. The solution uses HestiaCP on a VPS for reverse proxying, Let's Encrypt SSL certificates, and port forwarding on a home router to reach the TrueNAS instance at 192.168.0.17:30027. Additional steps cover configuring coturn for TURN relay to enable reliable voice and video calls, updating trusted domains in Nextcloud, and disabling router DoS protection. The setup also enables Screen Sharing, reactions, and push notifications while keeping all data under user control.