Yandex Black October: How Architectural Flaws and Capacity Mismanagement Turned Data Center Losses Into a 11-Day Fintech Coma
In October 2026 the Russian IT market witnessed an unprecedented infrastructure collapse when three Yandex data centers in Central Russia (Sasovo, Kaluga, Vladimir) were physically destroyed over four days. The outage brought down Yandex Cloud, halted services from Yandex Go to Yandex Direct, caused loss of up to seven days of data for some clients, and left the fintech vertical in an 11-day coma.
Public statements framed the event as an unavoidable military force-majeure. Architects examining the timeline, however, conclude that physical destruction was only the trigger; the scale and duration resulted from fundamental errors in distributed-system design, capacity management, and C-level risk assessment.
Chapter 1. Timeline of the Cascade: 74 Lost Hours
On 8 October at 01:31 MSK the Sasovo facility (ru-central1-b) was destroyed by drone attack and fire. By 14:00 serverless functions had failed across the platform. On 9 October the Kaluga site sustained damage. Only at 15:42, 38 hours after the first loss, did engineers provide tools to move Kubernetes control-plane nodes and clean dead database hosts from metadata. On 10 October surviving zones exhausted capacity and quota allocation was switched to manual mode.
At 04:00 on 11 October the Vladimir facility (ru-central1-a) containing the Galushkin supercomputer was destroyed. The remaining zones d and e could not maintain quorum. By 07:13 managed databases entered Read-Only, S3 stopped accepting writes, and Yandex Go, Yandex 360, Direct, Yandex Pay and external clients including CIAN, Dodo Pizza and the state VetIS system went offline.
Chapter 2. Why Raft and Multi-AZ Did Not Save the System
YDB and managed PostgreSQL clusters behaved exactly as CP systems should: they blocked writes when quorum was lost. The real failure occurred earlier. After Sasovo was lost, the Control Plane itself remained dependent on the dead zone, preventing Self-Healing and re-quorum operations for 74 hours. In addition, data-center utilization had been driven to near 100 percent in peacetime, leaving no spare servers or disks to rebuild the third replica.
All four primary sites lie within a 350 km radius of Moscow and share the same power and network backbone, forming a single correlated-failure domain. No physically isolated region such as ru-siberia existed, so a regional event became a nationwide blackout.
Chapter 3. The 11-Day Fintech Reconciliation
Fintech services remained offline far longer than ride-hailing or advertising because distributed sagas spanning Core Banking, the Split engine, payment gateways and Kafka/YDS event buses entered inconsistent states. Aggressive retry and at-least-once patterns without synchronized idempotency caches produced duplicate and phantom charges between 8 and 10 October. After 11 October engineers performed manual, transaction-by-transaction reconciliation against external ledgers and NSPK statements, a process completed only on 22 October.
Chapter 4. Root Cause at C-Level
KPIs rewarded GMV growth and CAPEX reduction while penalizing investment in remote DR regions or 35 percent spare capacity buffers. Threat models never accounted for simultaneous loss of three sites inside a single metro cluster. The result was an architecture that could survive a single rack or transformer failure but not the loss of an entire availability zone followed by a second.
Related articles
Passwork Comparison with OneKey Sparks Detailed Rebuttal from ABP2B on Security Claims
Passwork published a self-comparison of its corporate password manager against OneKey version 2.0.7, using simplified settings and an outdated release despite version 2.1.0 being available. ABP2B responded by highlighting biases in the analysis and noting that several features criticized as weaknesses are optional and can be disabled via group policies. The company released a major update shortly after, adding reworked authorization, enhanced formatted text protection, expanded cache controls, new group policies, strengthened server-side checks, and revised hash storage rules. Key technical disputes include the use of a single master password versus independent vault secrets, the correct application of Shamir's Secret Sharing to recovery keys rather than the master password, and the comparison of PBKDF2 iteration counts without considering the full cryptographic context. Additional points addressed the choice of GOST 34.12-2018 as the default algorithm for the Russian market versus AES-256, and the protective purpose of compromised password checking that organizations may optionally enable or disable.
How a Personal Site Counts Bots Without Storing Any IPs: Pure PHP, No Database, Strict CSP and 160 Tests
A personal website built entirely in pure PHP without frameworks or databases demonstrates advanced defensive security practices while tracking bot activity from an SSH honeypot. The site stores all content in a single JSON file with atomic writes and automatic backups, eliminating database-related attack surfaces and simplifying deployment to folder copying. Strict Content-Security-Policy rules prohibit inline styles and scripts without nonces, forcing the use of SVG attributes, CSSOM updates, and JSON data blocks instead of direct attribute injection. Over 160 automated tests written in PHP attack the site with XSS payloads, CSRF attempts, path traversals, and malformed Markdown to verify that no malicious output reaches the browser. Bot identification relies on behavioral signatures derived from the first twelve cleaned commands of each session, combined with HASSH fingerprints and activity patterns, allowing the site to report unique bot families and address counts without ever publishing IPs. Additional browser-based tests using Chromium validate accessibility, performance budgets, and CSP compliance across desktop and mobile viewports. The entire system runs with zero external dependencies and integrates tests directly into the deployment pipeline.
Russian Finance Ministry Seeks Central Bank Reports on Systematic P2P Transfers to Tax Authorities
The Russian Ministry of Finance has proposed amendments requiring the Central Bank to share data with the Federal Tax Service on individuals whose bank accounts show signs of regular income received from other private citizens. The changes target article 85 of the Tax Code and form part of the budget package bill numbered 617-9. Under the new rules, the Central Bank would identify such citizens through transaction analysis and transmit the information according to a future agreement with the tax service. The Federal Tax Service would also gain expanded powers to request bank statements from non-entrepreneurs without needing prior debt collection or audit triggers. If approved, the provisions would take effect on 1 January 2027 and apply to operations conducted after 1 January 2026. Separate bills under discussion would impose monthly transfer limits of 30,000 rubles on suspected clients starting in 2028 and require the tax service to notify the Central Bank about account openings and income categories.
Baidu Launches Ciyuan Exchange to Establish Trust Standards for AI Model Trading
Baidu Intelligent Cloud has introduced the Ciyuan Exchange, a dedicated trading platform for large AI models that aims to solve quality verification and credit issues in an increasingly crowded market. The platform, unveiled at the Baidu World 2026 Conference, already hosts over 100 supply resources with daily calls exceeding 50 million and daily token usage surpassing 700 billion. Founder Li Yanhong positioned the exchange as an infrastructure layer that moves beyond simple model aggregation toward verifiable identity, ongoing performance monitoring, and supplier credit records. The initiative addresses real procurement risks where identical models from different providers show up to twofold differences in throughput and reliability, according to a China Academy of Information and Communications Technology report. By combining model fingerprinting, capability testing, periodic audits, and continuous credit scoring, the platform seeks to create transparent market mechanisms similar to commodity exchanges. This development signals a broader industry shift from raw model capability competition toward standardized service quality, pricing transparency, and reliable delivery infrastructure.