English
Русский
Russian cloud provider Beget has encountered a critical incident that, by the company's own admission, has affected all levels of its architecture. Reports of the issues began surfacing around 3:00 AM MSK on November 2. According to Downdetector, approximately 9,800 user complaints were logged within a single day from those unable to access their resources.
The most notable detail of the ongoing situation is that, in an era of ubiquitous automation, the company's engineers were forced to resort to manual infrastructure configuration directly within the data centers. Teams are working in overdrive, attempting to piece together the shattered mosaic of services, although the exact root cause of the initial failure remains conspicuously absent from official statements.
The Domino Effect: From Ride-Hailing to Product Labeling
The scale of the accident has extended far beyond the provider's own servers, demonstrating a classic domino effect within the modern IT ecosystem. Users have mass-reported disruptions to the "Chestny Znak" product labeling service (978 complaints) and the BelkaCar ride-hailing platform (191 complaints). BelkaCar representatives have already confirmed that the root of the problem lies squarely in the accident on Beget's end, further highlighting the degree to which critical services rely on a single hosting provider.
Sanctions, Statistics, and Déjà Vu
According to the analytical portal StatOnline, Beget hosted 269,897 domains in October, holding a substantial 15.67% market share. This volume makes any downtime a nationwide event.
It is worth noting that this is not the first such episode in the provider's recent history. On June 2, Beget already reported accessibility issues with parts of its resources due to failures at backbone communication operators. Furthermore, in July, the company and its co-owners were hit with European Union sanctions over alleged service provision to government bodies and defense enterprises in specific regions. Given past experiences, it is safe to say that history has a bad habit of repeating itself, and cloud technologies sometimes still require very tangible, manual intervention.