Summary
- Sberbank acknowledges a drone strike at its Balakovo data centre in the Saratov region.
- The bank says systems continue operating normally and no staff were injured.
- Damage, failover, capacity effects and responsibility for the attack have not been independently verified.
Russian banking group Sberbank has confirmed a drone strike on its data centre at Balakovo in the Saratov region, saying that its systems and services continue to operate normally and that no employees were injured. The confirmation, reported on 14 October, concerns an attack acknowledged by the operator; it leaves physical damage and repair requirements unresolved. Responsibility for the strike has not been independently established in the available evidence.
Sberbank first deputy chairman Alexander Vedyakhin gave the company’s account of operational continuity. The statement does not include engineering inspection results, the number of affected buildings or rooms, or a description of which protective systems operated during the incident. Images circulated online have been described as showing damage, but their implications for computing equipment and critical services are not independently established.
Balakovo is part of Sberbank’s wider data centre estate. Public reporting says the facility was announced in 2020 and began construction the following year, with a phased development programme intended to continue through 2030. Reports describe a large campus and an ultimate electrical capacity exceeding 80 MW, but that planned end-state figure must not be presented as current connected or operational load.
Operations reported normal, damage assessment unknown
The bank’s assurance that services remain available is relevant to customers, yet it does not prove that every part of the site was unaffected. Facilities can retain service availability through surviving equipment, redundant systems, or workload distribution while a separate area is damaged. Without disclosure from the operator, no particular recovery mechanism can be attributed to the incident.
Physical damage and customer-facing service disruption can diverge when data centre systems have surviving power, network or computing resources. An attack can damage walls, roofing, utility connections, external plant, or internal systems with different consequences for the equipment that actually processes and stores data. The available reporting does not identify a verified failure point or establish which, if any, of these components were struck.
The incident follows several reported attacks on Russian data centre facilities, including sites operated by Yandex. DataCentral has previously covered the reported interruption to Yandex locations. Sberbank’s Balakovo incident is a separate company, site, and operator statement, although comparisons should not be used to infer identical damage or technical outcomes.
Continuity claims require later verification
Public information about the Balakovo build-out has referred to phased development and eventual high power demand. Large facilities of this type require multiple layers of physical security and service resilience, but the existence of a data centre campus does not establish the particular protections deployed. Detailed security arrangements have not been publicly confirmed in connection with this attack.
The immediate operational measure available is the bank’s own statement. There are no independently published metrics showing service interruption, automatic failover activity, equipment losses, repair cost, or reduced usable capacity. The absence of those disclosures should not be mistaken for evidence that no physical impact occurred.
Sberbank has disclosed neither an engineering damage assessment nor a programme of repairs. Its statement of uninterrupted service remains the only identified operator account of availability following the strike, with no independently quantified loss of equipment or capacity.
