Yandex Cloud

Yandex Black October: How Architectural Flaws and Capacity Mismanagement Turned Data Center Losses Into a 11-Day Fintech Coma

In October 2026 three Yandex data centers in Central Russia were physically destroyed within days, triggering the collapse of Yandex Cloud and multiple core services. Between the first and third site failures engineers had 74 hours to restore quorum and rebalance workloads yet failed to do so because Control Plane components remained tied to the lost zone and spare capacity had been eliminated to cut costs. Core banking and BNPL systems entered Read-Only mode after losing quorum, forcing a complete stop-the-world reconciliation that lasted until 22 October. Backups stored inside the same regional S3 buckets proved unusable, resulting in a seven-day RPO and primary-key collisions after restoration. The incident exposed that Metro-Cluster designs had been incorrectly treated as full Disaster Recovery and that aggressive AP microservice patterns created logical split-brain conditions outside the database layer.

AI Investigators in SOCs: Limits of Autonomy, Prompt Injection Risks, and the Cost of Over-Reliance

A February 2026 Vectra AI survey of 1,450 security professionals revealed that organizations receive nearly 3,000 daily attack alerts on average, with 63% left unprocessed and 71% of respondents delaying critical tasks at least two days a week. The article examines the push to deploy autonomous AI agents for investigations in Security Operations Centers, highlighting how such systems often fail when confronted with real-world disorder such as inconsistent server timestamps, unapproved software installations, and incomplete logging. It stresses strict limits on AI decision-making authority, especially for blocking systems or revoking access, and warns against treating model confidence scores as reliable error probabilities. Prompt injection attacks via malicious emails, logs, or documents are identified as a novel threat that can manipulate language models into ignoring attacks or leaking data. Research from Microsoft involving 167 analysts showed that false “safe” verdicts from AI increased missed threats by 29 percentage points. The piece concludes that independent human verification of AI-closed cases remains essential to avoid hidden risks behind empty alert queues.

Yandex Restores Taxi, Delivery and Mobility Services After Major Infrastructure Outage

Yandex has announced that its core transport and delivery services are once again available to all users following a large-scale infrastructure failure. The affected services include ride-hailing, food and grocery delivery, car-sharing, electric scooters, and smartphone charging stations. Additional platforms such as Lavka, Zapravki, and Transport have also returned to normal operation. Recovery remains gradual, with some Yandex 360 features intentionally disabled to manage load after earlier partial restoration of search, Alice, Maps, and Mail on 11 October. The company is providing free resource usage for Yandex Cloud and Yandex 360 customers in Russian availability zones from 8 to 31 October, with automatic billing adjustments. Director of Strategic Marketing Andrei Sebrant stated that the incident exceeded the severity of a single data-center loss scenario practiced in drills.

Rostelecom Calls for 'Doomsday' Data Centers to Counter Drone Attacks and Infrastructure Risks

Rostelecom executive Valery Ermakov has urged Russian companies to build geographically distributed backup data centers, dubbed 'doomsday' facilities, to ensure service recovery after site losses. The recommendation follows drone strikes that disabled three Yandex data centers in Sasovo, Kaluga, and Vladimir, disrupting both internal services and Yandex Cloud clients. Ermakov explained that previous centralized infrastructure, built for economic efficiency, is no longer viable under changed threat models that now include physical attacks previously considered unthinkable. He advocated a micro-cellular architecture with services spread across many sites connected by high-speed links, while warning that Russian backbone networks are overloaded and much fiber optic infrastructure dates back 20-30 years. Rostelecom positioned its TEA NEXT line running from Kaliningrad to Mongolia as a source of additional capacity to address potential backbone shortages. Yandex responded to the incidents by accelerating client data migration to partner cloud providers.

VK Shares Rise 7.62% as Market Assesses Data Center Developments and Yandex Cloud Challenges

VK shares climbed sharply on October 12, reaching a peak increase of 7.62% to 134.2 rubles before moderating to a 6.6% gain at 132.95 rubles by evening. Analysts from Freedom Global linked the movement partly to the Ministry of Digital Development's announcement of joint measures with the Ministry of Defense to protect Russian data centers. Other observers at Finam suggested investors were pricing in potential client shifts from Yandex Cloud to competitors such as VK Cloud, which has already begun accelerated infrastructure placement for affected Yandex customers. The surge was also attributed to broader capital rotation away from the energy sector toward previously lagging technology stocks. While the confirmed price movement is clear, the exact drivers remain analytical interpretations rather than verified revenue impacts. The episode highlights how regulatory and infrastructure news can quickly influence valuations in the Russian cloud services market.

Yandex Data Center Attacks Trigger Outages, Cloud Disruptions and Stock Decline

A series of physical attacks has disabled or partially damaged multiple Yandex data centers in Russia, leading to prolonged service outages across cloud and consumer platforms. Fires and power failures struck facilities in Sasovo, Kaluga and Vladimir between 8 and 11 October, forcing the company to shift workloads to the remaining Mytishchi site. Analysts from Finam, Rikom-Trust and Freedom Global note that recovery timelines now stretch from several months to two years for specialized hardware such as supercomputers. The incidents have already erased nearly 9 percent of Yandex share value and raised concerns over future capital expenditure, client retention in Yandex Cloud and potential sanctions complications for overseas expansion. Experts emphasize that the attacks have moved from isolated technical failures to a systemic business-continuity and investment-risk issue.

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.

Alfa-Bank Balances Cloud Trust and Zero Trust Models During Migration to Yandex Cloud

Alfa-Bank's head of container and cloud security, Sasha Chertok, detailed how the bank migrated regulated workloads to Yandex Cloud while preserving existing Zero Trust controls. The organization mapped on-premises network segmentation, Active Directory authentication, and firewall policies directly onto Yandex Cloud resources using interconnect links secured with GOST encryption. Responsibility for managed services is shared under a Cloud Trust model, yet the bank retains oversight through Terraform-managed Security Groups, custom CSPM checks, and internal CI/CD gates. User access continues to authenticate via on-premises Active Directory and KeyCloak federations, while authorization leverages granular Yandex Cloud IAM roles. Logging and detection rely on a combination of Yandex Cloud Audit Trail, Cloud Logging, and the YCDR service to compensate for incomplete control-plane visibility. The resulting hybrid architecture now supports 1,500 virtual machines, 100 managed services, and 1,000 identities across multiple environments without disrupting established security processes.

10 Non-Obvious S3 Integration Vulnerabilities Exposed in Web Application Bug Bounty Research

Security researcher Sergey Bobrov, known as BlackFan, published a detailed analysis of S3 misconfigurations when integrated into web applications via proxies such as nginx. The article examines ten laboratory setups demonstrating issues ranging from stored XSS and bucket takeover to rewrite rule bypasses and cache poisoning. Key findings highlight how nginx path normalization differences, missing trailing slashes, and variable usage like $uri enable attackers to reach arbitrary buckets or inject HTTP request splitting payloads. The research covers both direct S3 client usage and proxy-based integrations, emphasizing ACL and Bucket Policy errors that expose data to any authenticated S3 user worldwide. Practical demonstrations include exploitation of Ceph RGW path traversal with ../ sequences and cache key collisions via response-content-type parameters. The work provides fingerprinting tables for identifying S3-compatible systems including MinIO, Ceph RGW, and Yandex Cloud based on headers and error responses.

Over 15,000 Companies Deploy AI Agents to Combat Cloud Cyberattacks

More than 15,000 companies are already using AI-powered information security services in public clouds to detect attacks in real time, triage alert streams, and address vulnerabilities faster than human teams can process thousands of notifications. Yandex Cloud's threat report for the first half of 2026 shows attackers moving away from stolen passwords toward exploiting vulnerabilities in public applications. Specific attempts observed in Russian clouds include the critical React2Shell flaw along with Linux kernel issues Copy Fail and Dirty Frag. Companies are handing routine tasks such as alert prioritization, incident data collection, and initial investigations to AI agents while keeping human oversight for critical vulnerability remediation. The report notes that retail has become the top attack target at 39 percent, followed by manufacturing at 29 percent, while the IT sector dropped to 20 percent. Modern defenses now require behavioral detectors, unified telemetry, and AI agents to match the accelerated pace of attacks.

Certificate Transparency Logs Fail to Block Rogue CA Man-in-the-Middle Attacks

A detailed technical analysis reveals that Certificate Transparency logs do not effectively protect users from man-in-the-middle attacks carried out with certificates issued by compromised or sloppy certificate authorities. The author attempted to verify SCT entries from real browser certificates using public CT log APIs such as get-proof-by-hash but consistently received 404 Not Found responses. Tools including Windows certutil also reported every SCT as not found in the logs. A practical proof-of-concept attack was then constructed by creating a self-signed CA that exactly replicated the certificate chain of habr.com and serving it through nginx with matching extensions and attributes. The resulting MITM connection was accepted by browsers without warnings despite HSTS, because the pre-certificate in the log differs from the presented certificate only in public key bytes. A publicly accessible demonstration was deployed on Yandex Cloud allowing anyone to test the bypass by overriding DNS for habr.com.

Yandex Cloud Partners with Sogaz and Ingosstrakh to Automate Cyber Risk Assessment for Business Insurance

Yandex Cloud, through its Yandex B2B Tech division, has launched joint cyber insurance programs with Russian insurers Sogaz and Ingosstrakh. The initiative replaces traditional manual questionnaires with automated infrastructure scanning via the Yandex Security Deck service. The tool examines cloud resources, applications, and data to identify open internal information, excessive user privileges, leak risks, and potential compromise vectors. Detected issues are consolidated in a single prioritized interface and shared with insurers to refine policy terms. If critical gaps are found, Yandex Cloud also provides remediation recommendations. The move comes as demand for cyber insurance grows rapidly, with Sogaz reporting that requested coverage volume doubled year-over-year to exceed 12 billion rubles in the first half of 2026.

TSPU Filtering Disrupts Timeweb Cloud Servers: Diagnosis, CDN Failures, and Reverse Proxy Bypass

Russian hosting provider Timeweb Cloud experienced widespread TSPU-based DPI filtering starting in early June that selectively blocked TLS handshakes on port 443 while leaving SSH, ICMP, and TCP connectivity intact. The issue affected multiple providers including Beget and Selectel, was publicly acknowledged by Timeweb on June 5, and proved highly variable by region, operator, and time of day. Attempts to mitigate via new IP addresses or Timeweb's own CDN failed due to poisoned caches and platform outages, while Yandex Cloud CDN blocked all POST requests required for WordPress functionality. A working solution involved deploying a minimal nginx reverse proxy on another Russian cloud VPS that preserves full HTTP methods, handles certificate synchronization, and routes ACME challenges correctly. Timeweb support later closed tickets without resolution after requesting ineffective mtr traces that cannot detect DPI behavior. The case highlights systemic challenges in diagnosing state-mandated filtering and the limitations of standard network diagnostics against selective TLS interference.

Solar inRights 3.11 Automatically Blocks Corporate Accounts Whose Passwords Appear in Dark Web Leaks

GC Solar has released Solar inRights 3.11, a major update to its identity and access management platform that integrates directly with the Solar AURA threat monitoring service. The new version automatically detects corporate credentials exposed in open sources and dark web dumps, validates whether the same login-password pairs remain active inside the organization, and instantly revokes access while alerting the security team. The feature addresses the common scenario in which employees reuse work email addresses and passwords on third-party websites, allowing attackers to test stolen credentials against corporate systems in what appears to be legitimate login attempts. Research cited by Solar shows that a single large Russian company typically has more than 600 unique corporate accounts circulating in public and underground sources, although only about 4 percent directly indicate infrastructure compromise. Yandex Cloud data further reveals that valid account abuse featured in 54 percent of over 25,000 attacks on cloud and hybrid environments during the first half of 2025. In addition to the leak-response capability, version 3.11 introduces improved search, request filtering, and integration templates for Active Directory, Exchange, and 1C.