Summary
- A Russian strike critically damaged GigaCenter's Kyiv facility on 20 October, leading to an indefinite operational suspension.
- GigaCenter says its employees are safe and customers will receive individual updates about their equipment.
- Affiliated GigaCloud reports service continuity through backup sites in Ukraine and the EU, although this does not establish the condition of all customer hardware.
Ukrainian colocation provider GigaCenter has suspended operations at its Kyiv data centre indefinitely after a Russian strike on 20 October caused critical damage and rendered the facility inoperable.
The operator confirmed the suspension on 21 October, following an earlier statement warning that customers could experience interruptions to equipment hosted at the site. GigaCenter said its employees were safe and that customers would receive individual information about the condition of their systems.
GigaCenter provides accommodation, power, cooling, connectivity, and supporting services for business computing equipment. Its Kyiv facility opened in 2014 and had previously been described as supporting approximately 300 racks.
The site covers around 1,200 square metres, including approximately 550 square metres of IT accommodation, according to specifications published before the attack. Those figures describe the facility’s original design and do not establish how much customer equipment was installed or damaged on 20 October.
GigaCenter initially reported that its facility had been struck and that technical teams were working to contain the consequences. Later the same day, the company described the damage as critical and confirmed that it could no longer continue operating the site.
The suspension has no announced end date. The operator has not provided a detailed account of the damage to its building, electrical infrastructure, cooling equipment, or telecommunications connections.
It has also not disclosed the number of affected customers, the amount of equipment that can be recovered, or the cost of restoring or replacing the facility. These questions will influence the practical options available to businesses whose hardware was hosted there.
GigaCenter belongs to GigaGroup, alongside telecommunications operator GigaTrans, cloud provider GigaCloud, and cybersecurity company GigaSafe. The group’s activities involve different services and infrastructure arrangements, so the closure of its colocation site should not be treated as evidence that every associated operation has stopped.
GigaCloud separately acknowledged that one of the data centres hosting its services had been damaged. It said its cloud customers continued receiving services through decentralised backup locations in Ukraine and the European Union.
The cloud provider has identified a wider network of facilities supporting its operations, including sites in Warsaw and other European locations. Its statement indicates that alternative infrastructure remained available, but it does not establish which applications were moved, how capacity was distributed, or whether every recovery process was completed without interruption.
Nor does GigaCloud’s account establish the condition of servers belonging to independent colocation customers at GigaCenter. Those customers may operate their own equipment and recovery arrangements rather than using the cloud provider’s replicated services.
The difference between physical colocation and cloud recovery becomes particularly important when an entire site is unavailable. A colocation customer may need to establish whether equipment has survived, recover usable data, obtain replacement hardware, and arrange sufficient hosting capacity elsewhere.
Applications designed to run across separate cloud locations may have more options for continuing service, provided that data replication, networking, authentication, and computing resources remain available. Recovery still depends on the architecture of individual services and cannot be assumed from the number of facilities listed by a provider.
The incident follows a separate Russian attack affecting the Kyiv data centre of telecommunications operator Datagroup. Datagroup reported that its infrastructure was destroyed following a strike during the night of 19 October, while customer services continued through reserve arrangements.
The two events concern different operators and physical installations. GigaCenter’s facility was struck on 20 October, and its indefinite closure was confirmed on 21 October. They must not be combined into a single incident or described as damage to the same building.
Both cases expose limits in resilience arrangements designed primarily around equipment failure. Data centres may incorporate multiple electrical feeds, backup generators, uninterruptible power supplies, redundant cooling equipment, and diverse telecommunications connections.
Such measures can improve service continuity following individual component failures or maintenance activities. Their protection is more limited where extensive physical damage prevents safe access to a facility or disables several supporting systems simultaneously.
Geographically separated infrastructure addresses a wider class of failures by reducing reliance on one building or local utility network. It also introduces additional requirements for data replication, bandwidth, application design, capacity reservations, and operating procedures.
The practical effectiveness of those arrangements depends on whether customers have tested their recovery processes and whether alternative sites can support the required workloads. A declared recovery capability does not necessarily mean that every application can resume immediately or without losing recent data.
The consequences of a major physical incident can extend beyond restoration of computing services. Equipment ownership, access to the damaged premises, insurance, secure disposal, data protection, and customer communications may all require attention before the operator can establish a longer-term position.
GigaCenter has committed to informing customers individually about their equipment, but no general recovery timetable has been announced. The company has not stated whether it will rebuild at the same location or seek a replacement facility.
Its Kyiv colocation operation therefore remains suspended indefinitely. GigaCloud continues to report service availability through distributed infrastructure, while the condition of individual customer installations at GigaCenter remains to be established.
