At the moment, we cannot give deadlines for the restoration of services, but we are making every effort to improve the situation.

You can delete the resources:

• of one folder,

• of an entire cloud’s resources.

If the infrastructure is located in a zone without power, deletion operations are not available. Please keep an eye on the status.

Resources that are currently unavailable are not charged and will not be taken into account when calculating consumption. They may appear by mistake in the billing account details, but they will not be charged.

Top-ups of account balances are available once again. You can check your current balance in Yandex Cloud Billing: select your billing account and open the Account page. If you have already topped up your balance, you can check it in the Payment History section in the left-hand panel. It shows the date, status, and amount of the payment. For more details, read the instructions.

The use of all Yandex Cloud services in all availability zones of the Russian Federation will be free of charge for current customers from October 8 to October 31, inclusive.

The October invoice will only reflect expenditures on resources used up to and including October 7.

Charges for the period from October 8 may still appear in the billing account, but we will correct them automatically.

Read more on our site.

Use the instructions that will help you transfer data from a disk image or section of a running virtual machine.

If you need new computing power, consider using Yandex BareMetal servers. There are separate quotas for them.

You will not be able to transfer virtual machine snapshots or Cloud Backup backups to BareMetal. To transfer, use methods for transferring data from running VMs to a BareMetal server at the operating system and application levels.

The console displays the correct status of the operations of the target groups of load balancers and Instance Groups.

You don’t need to do anything right now with clusters that have two masters available.

If you need new computing resources, consider creating external groups of nodes with other providers.

We do not recommend stopping a cluster to restart it: the stop operation may freeze and block its launch.

Before creating or increasing a node group, check the available quotas in the selected zone. Keep in mind that the creation and modification of groups are also limited by the availability of free computing resources. For some of the affected clusters, operations with node groups may be suspended.

If you are deleting a cluster or node group to free up resources for new ones, wait for the deletion to complete and check the available quotas. The operation may freeze, and the related computing resources and quotas may not be released immediately.

To increase the available resources in a cluster, we recommend you consider creating BareMetal node groups in Managed Service for Kubernetes^®.

Groups can be created via the Cilium cluster UI on Kubernetes^® version 1.35.

If your cluster meets these requirements, BareMetal node groups can be an additional way to expand its resources.

You can use Data Transfer to export data from any database. We described how to prepare databases for migration in the documentation.

When creating new clusters in Yandex Data Processing, Yandex Managed Service for Apache Spark^™, and Yandex Managed Service for Trino, we recommend you not use intermittent capacities and disable autoscaling. Use a fixed cluster size. We recommend you move all data from HDFS and local drives to S3. For more details, read the instructions.

For correct and stable operation of speech recognition (STT) and speech synthesis (TTS), switch to API v3.

We recommend using synchronous mode, but it may be delayed. Asynchronous mode works only from 00:00 to 06:00 (Moscow time).

For generative search in the internet, we recommend using the Responses API and Web Search Tool instead of the Yandex Search API generative response. Instructions can be found in the documentation.

Join the community chat, where we quickly answer questions: Telegram.

The service processes newly uploaded files as usual. All previously unprocessed data has been processed. The functionality for recalculating Pro tags and assistants has been restored.

Use the DeepSeek V4.1 Flash model.

If you receive a 403 error when trying to log in to your workspace, delete the workspace and create a new one.

We have restored MCP and related plugins.

New users should contact the support service to increase their quota before launching the service for the first time. It may take time to process the request.

Join the AI2Business community chat in Telegram where we quickly answer questions.

Use an external model by default. If you need a local one, select it in the platform interface according to the instructions.

Join the community chat where we quickly answer questions: Telegram, VK.

We recommend creating a service account (or several) in the Yandex Cloud catalog, and granting it rights to manage resources and create authorized keys (or other types of keys if necessary) to use it to manage infrastructure via CLI/Terraform.

Example command:

yc resource-manager cloud add-access-binding --cloud-id=<...> --service-account-id=<...> —role=<...>

The service is working with temporary restrictions:

• Traffic filtering continues on current ALB resources and proxy servers. Automatic scaling is temporarily unavailable.
• You can change the security settings and proxy server configurations.
• Creating new proxy servers and manually scaling ALB resources and proxy servers are temporarily unavailable.
• Viewing service logs and monitoring data is temporarily unavailable.

We have restored the functionality of the Configuration Control (CSPM) and Kubernetes Control (KSPM) modules.

You can connect new cloud resources and Kubernetes clusters for purposes of inventory, identifying configuration errors, and to verify compliance with security requirements and standards.

We have also restored operations with alerts in these modules: viewing, processing, and exporting results.

The rest of the Yandex Security Deck modules are temporarily working with restrictions.

We recommend you download and save the results of current checks in the Data Control Module (DSPM).

Configuration level events can be transferred to Object Storage buckets and Yandex Data Streams. To ensure the collection and storage of audit events, we recommend creating trails with events exported to Object Storage and Yandex Data Streams.

To manage access to third-party cloud platform resources centrally and securely, we recommend setting up single sign-on (SSO) via Yandex Identity Hub.

Typical pretexts used by fraudsters include: “your data is damaged — log in to recover”, “your account blocked as the result of a failure”, “enter your details to receive compensation for downtime”, “urgent migration — open this attachment”.

We never ask for passwords, 2FA codes, API keys, card details, or remote access via email.

How to recognize fraudsters

• Sender: A real address can only be on the @yandex.cloud domain.
• Links: Hover before clicking; HTTPS ≠ security. Instead of clicking on a button in an email, open the site manually.
• Urgency: Phrases like “you must confirm within 24 hours” are sign of an attack.
• Attachments: Do not open .exe, .js, .zip with a password, or .docm files.

What you should do

1. Only check the status of platform components on the status board and the console.
2. When in doubt, do not click. Check our official channel.
3. Mark suspicious emails as spam.

If you have already entered data

1. Change your password.
2. Log out of all sessions.
3. Check your mail forwarding rules.
4. Report the incident to the support service via the console.