The 2011 MHost Datacenter Collapse: How a Hosting Provider Vanished Overnight and the Hard Lesson About Backups
In October 2011, the Ukrainian hosting industry witnessed one of its most notorious and cautionary scandals: over a single weekend, MHost (mhost.ua), a prominent Kyiv datacenter, vanished without a trace, leaving hundreds of webmasters and businesses stranded without servers, databases, or backups.
Customer support phone lines went completely dead, the provider’s official domain was pointed to a local loopback IP 127.0.0.1, and all physical hardware — both rented servers and customer-owned colocation gear — was unbolted from the racks and hauled away in moving trucks. As an active customer who had neglected off-site backups for over three months, I received a harsh, unforgettable wake-up call about data resilience.
What Happened to MHost in October 2011
On the night of October 22–23, 2011, all servers hosted in the MHost facility went offline simultaneously. Phone calls to their Kyiv support desks went unanswered, and former employees began posting on IT webmaster forums that management had quietly fired the entire staff retroactively.
Subsequent investigations revealed that beneath the glossy corporate facade, the facility was crippled by mounting building lease debts, unpaid utility bills, and fierce shareholder infighting. Customers rushed to the datacenter premises, but most never recovered their physical hardware or their data.
Personal Experience: The Warning Signs Before the Collapse
I had been renting a dedicated server from MHost for about a year. The warning signs were obvious in hindsight, and they reflect the typical red flags of a struggling hosting provider:
- Frequent network drops: the server lost connectivity almost weekly for dozens of minutes, with support habitually blaming “yet another massive incoming DDoS attack.”
- Unreliable KVM-IP access: during an urgent server freeze, support demanded a “formal written ticket,” kept me on hold for 20 minutes, and finally admitted their KVM-over-IP module was broken before simply power-cycling the server by button.
- Irony of marketing slogans: the company ran lavish promotional campaigns branding itself as a fortress of digital security. Their promo video famously concluded with the tagline: “MHost — the impenetrable fortress of your information!”.
The Evergreen Sysadmin Lesson: The 3-2-1 Backup Rule
The MHost disaster proved a fundamental rule of systems administration: no matter how reputable a datacenter looks, hardware and facilities can vanish overnight. A backup stored on the same machine, or even in the same building, is not a backup.
To safeguard critical projects from unforeseen provider failures, every sysadmin and site owner should enforce the battle-tested principles of disaster recovery:
- The 3-2-1 backup rule: maintain at least 3 copies of your data across 2 different storage media, with at least 1 copy hosted completely off-site (an independent cloud provider, S3 bucket, or off-premises NAS).
- Automated schedules: backups must be triggered automatically via scripts (daily for databases, weekly for static assets), never relying on manual weekend routines.
- Regular restore drills: a backup only truly exists once you have successfully restored and verified it in an isolated staging environment.
Around the same time, servers were seized by authorities at the “Kolokol” datacenter in Dnipro. However, sites with independent off-site backups were restored and running again within hours. Never rely entirely on your hosting provider’s promises — verify your off-site backups today!