Yandex 360

Yandex Restores Access to 96% of Yandex Disk Data After Data Center Attacks

Yandex has recovered access to 96 percent of user data stored on Yandex Disk following attacks that damaged its data centers. Files including documents, photographs, and videos are once again available for opening, downloading, and sharing for the majority of users. The company continues to redistribute Disk capacity across independent external sites to improve overall resilience. Basic operations such as uploading, downloading, and synchronization are now functional, yet the web version still imposes restrictions on bulk actions like downloading entire folders or multiple files at once. Users are advised to rely on the desktop client or API for these tasks during the remaining recovery phase. Yandex publishes ongoing updates on the official Yandex 360 service status page and has not provided an exact date for full restoration.

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.

Yandex 360 Email Archive Documentation Shows Search Snapshots and Former Employee Log Filters

The Yandex 360 administrator guide describes the email archive as a tool that stores copies of all messages sent and received by employees on the organization's domain. Two specific statements in the documentation indicate that each saved search returns a static snapshot that does not update automatically when new mail arrives, requiring manual cloning or recreation of the search to obtain current results. The same documentation states that the action log records every operation performed in the archive, yet the employee filter in the log interface only displays currently active accounts, making it impossible to select a former administrator by name. API 360 currently provides no documented endpoints for creating, executing, or retrieving archive searches, leaving all operations dependent on the web console. Additional notes clarify that messages remain available after an account is blocked but disappear once the account is deleted, and that messages removed before the archive was enabled cannot be recovered. These documented behaviors directly affect incident response and offboarding procedures that rely on historical email retrieval and audit trails.

Measuring Data Leak Risk by Days of Silence Rather Than Megabytes in Cloud Environments

A financial expert turned security specialist argues that the true cost of data leaks in cloud offices stems not from the volume of exposed files but from the duration they remain undetected. The article details how routine actions such as making documents public, forwarding emails externally, or changing passwords can silently expose sensitive information in platforms like Yandex 360 without triggering any alerts. It warns against blanket prohibitions that push risky behavior into unmonitored channels like personal email or messengers, reducing visibility to zero. Instead, the recommended approach focuses on real-time event-driven notifications combined with automated remediation to minimize the window of exposure. The piece provides a detailed checklist for evaluating monitoring tools, including immediate reaction capabilities, self-healing actions, regular overview reports, and proof of system health. Emphasis is placed on secure integration via OAuth, data residency compliance, and the importance of treating employees as hurried professionals rather than malicious actors.