Servercore.Status

Bare metal Operational

Pools Operational

TAS-1 Operational

TAS-2 Operational

ALM-1 Operational

NBO-1 Operational

NSK-1 Operational

MSK-1 Operational

MSK-2 Operational

MSK-3 Operational

MSK-7 Operational

SPB-1 Operational

SPB-2 Operational

SPB-3 Operational

SPB-4 Operational

SPB-5 Operational

Services Operational

Dedicated Servers Operational

Network Operational

Secrets manager Operational

Cloud Platform Minor incident

Pools Minor incident

uz-1a Operational

uz-2a Minor incident

kz-1a Minor incident

ke-1a Operational

ru-1a Minor incident

ru-1b Minor incident

ru-1c Minor incident

ru-2a Operational

ru-2b Operational

ru-2c Operational

ru-3a Minor incident

ru-3b Minor incident

gis-1a Minor incident

ru-6a Minor incident

ru-6b Operational

ru-6c Operational

ru-7a Operational

ru-8 Operational

ru-9a Operational

Services Minor incident

Cloud servers Operational

S3 Minor incident

Network Volumes Operational

Images Operational

Backups Operational

Load Balancer Operational

Network Operational

Managed Kubernetes Operational

Managed Databases Operational

File Storage Operational

Network services Operational

DNS-hosting Operational

Anti-DDoS Operational

Global router (L3VPN) Operational

Data centers Operational

Tashkent, Uzbekistan Operational

Almaty, Kazakhstan Operational

Nairobi, Kenya Operational

Infrastructure Operational

Electricity Operational

Conditioning Operational

Redundancy Operational

Network Operational

Interfaces Operational

Website Operational

Control Panel Operational

Billing Operational

API Operational

Mirror Operational

NTP Operational

Mail Operational

External network Operational

DNS Operational

External network Operational

Mail service Operational

Current incidents

Minor incident Problems accessing S3

[Issue]

Currently, we are seeing an increased intensity of calls to S3 service in the regions ru-1, ru-3, ru-6, ru-7, gis-1, kz-1, uz-2.

In this regard, it is possible to increase the response time and temporarily decrease the speed during operations of reading and writing objects. Data availability is maintained in full.

Work on load balancing is already underway on our part.
We apologize for any inconvenience.

Information notices

Information notice Support response times are temporarily longer than usual

[Information]

If you have technical questions, a wide range of topics is covered in the documentation.

If you need help from a specialist, please submit a ticket. However, responses may currently take longer than usual.

Scheduled maintenances

Scheduled maintenance Scheduled maintenance of the Cloud platform infrastructure: virtual machines, Managed Databases, and Managed Kubernetes clusters from 2026-10-26 10:00 EAT to 2026-10-26 19:00 EAT

[Scheduled]

From October 26 at 10:00 to October 26 at 19:00 (UTC+03:00), we will perform a scheduled upgrade of the Cloud platform infrastructure. This maintenance is required to improve service stability.

During the maintenance, Cloud platform hosts in the affected pools will be rebooted. Virtual machines, database clusters, Managed Kubernetes worker nodes and basic clusters will be unavailable for up to 15 minutes.

The maintenance will be carried out sequentially in each pool segment. This will help...

Scheduled maintenance Scheduled maintenance of the Cloud platform infrastructure: virtual machines, Managed Databases, and Managed Kubernetes clusters from 2026-10-26 23:00 EAT to 2026-10-27 07:00 EAT

[Scheduled]

From October 26 at 23:00 to October 27 at 07:00 (UTC+05:00), we will perform a scheduled upgrade of the Cloud platform infrastructure. This maintenance is required to improve service stability.

The maintenance will be carried out sequentially in each pool segment. This will help...

Past incidents

Scheduled maintenance Electrical Equipment Maintenance at MSK-7 from 2026-10-22 09:00 EAT to 2026-10-22 20:00 EAT

[Resolved]

This maintenance has been concluded as planned.

Minor incident The problem with delayed recording on network drives in the ru-6 region

[Resolved]

At the moment, the network drives are functioning again.

Incident & maintenance history

This page is automatically updated every 60 seconds