The Deadpool Files - Part 4

A history of hosting providers that vanished with customer data, told through real, named community threads from lowendspirit.com and lowendtalk.com. A series in many parts

When the company itself goes bankrupt

Most of the providers in this post were shadowy in some way, thin websites, unclear ownership, brands that existed to sell cheap VPS plans and not much else. GetServers was different: the trading name for 27Fibre Ltd, a registered UK limited company based in Manchester, running real dedicated and VPS hosting out of real facilities, with a real legal existence that went through a real, formal liquidation in June 2024.

Customers were told to remove their data by a hard deadline, June 30, 2024, 5pm British time, after which access would end for good. The company stopped accepting new payments before that cutoff, which is itself a small, telling detail: a company mid-collapse still had enough institutional order left to stop taking money it knew it couldn't honor, rather than squeezing out a few more weeks of prepayments from customers who had no idea the end was already decided. The lowendtalk.com thread that tracked the shutdown was titled, bluntly, "GetServers / 27Fibre deadpool - PLEASE RESCUE OFFERS", the community's term for the scramble that happens whenever a dying provider's hardware and remaining contracts become available at fire-sale prices before the lights go out for good, as people who'd been eyeing 27Fibre's rack space for months suddenly had a closing window to make an offer.

Liquidation in the UK is a formal, court-recognized process, a licensed insolvency practitioner takes control of the company's remaining assets, creditors get to make claims against whatever's left, and the company is eventually struck off the official register. None of that machinery exists to help a customer get their VPS data back; it exists to sort out who gets paid what from whatever value remains once the company can no longer operate. A customer's data isn't a creditor claim. It's just gone, on the same hard deadline as everyone else's, regardless of how orderly the underlying legal process looks on paper.

A formal liquidation is a different animal from a silent vanish, even though it lands the same way for the customer holding the bag when their VPS stops responding. There's a legal process, a deadline instead of a guess, and in principle a paper trail, filed with UK Companies House, part of the public record, that survives the company itself even after the website goes dark. It doesn't get anyone's data back or their money refunded any faster than a scam would. But it's the difference between a company that broke the law on its way out, the way VolumeDrive would a decade earlier, and one that, however painfully, followed the process that exists for exactly this situation.

The "PLEASE RESCUE OFFERS" title deserves a second look, because it captures a ritual that shows up again and again whenever a provider's death comes with any lead time at all. The moment word gets out that a host is closing, a specific subset of the community shows up not to mourn but to shop, people who've been eyeing a competitor's rack space, IP allocations, or leftover hardware contracts for months and suddenly have a closing window to make a lowball offer before it's gone for good. It's a small, slightly mercenary tradition, and it exists because dying infrastructure at a fire-sale price is one of the only genuine bargains left in a market already built around rock-bottom pricing.

There's something almost reassuring, in a strange way, about a deadpool that follows a legal process rather than skipping town in the night. Customers of 27Fibre knew, to the hour, when their access would end. They knew the company had a real registered address, a real board, real obligations under UK company law that didn't simply evaporate because the business had. None of that got their VPS data back. But it meant nobody had to spend weeks wondering whether the company still existed somewhere, still owed them something, still might reappear with an explanation that never came, the specific, low-grade uncertainty that haunts several of the other cases in this post long after the servers actually went dark.

A registered UK Ltd is also, unlike most of this post's brands, a matter of public record before it ever fails, anyone could have looked up 27Fibre Ltd's filing history on Companies House the day they signed up, and seen exactly how long the company had existed and who was behind it. That kind of transparency doesn't prevent failure. It just means the failure, when it comes, isn't a mystery on top of a loss.

That distinction matters for anyone trying to read the warning signs on a provider before it's too late. A registered limited company with real UK corporate filings is not automatically safer than an anonymous LowEndBox brand with no paperwork behind it, 27Fibre still failed, still left customers scrambling on a 48-hour data-removal deadline, still ended the same way for the people whose servers went dark. But when the end comes, a company that exists as a real legal entity has fewer places to hide, and its failure leaves a trail that outlives it. That's cold comfort to someone who just lost their VPS. It's not nothing, either.

Dead for a month before anyone noticed

Not every deadpool ends in outrage. Some end in something almost funnier and sadder at once: a company dies, and nobody notices for weeks. HT-Hosting, a small German host, had already earned a reputation on the forums as chronically troubled, the kind of provider regulars would half-jokingly call "hopelessly incompetent" in threads like "My HT-Hosting review" and "HT-Hosting.de is not a good provider," both written well before it actually shut down. It had been hacked at one point, cycled through repeated bouts of downtime, and at one low point sent customers apology messages that read like they'd been drafted by ChatGPT, along with free service credits meant to smooth things over and buy the company a little more goodwill than its track record had earned.

Then, without any announcement, it simply stopped. No shutdown notice, no final email, nothing resembling the countdown that DediPath's or the twenty-brand scam ring's customers had gotten. The thread that eventually surfaced the news carried a title that says everything about how anticlimactic it was: "Seems no one on LET even noticed that HT-Hosting deadpooled." Refunds that had reportedly been promised to customers during the earlier rounds of trouble never actually arrived, according to the forum's own account, money that was owed simply stayed unpaid once the company stopped existing to pay it, one more small debt absorbed into the general pattern of nobody expecting much from HT-Hosting in the first place.

What makes this one worth including isn't drama. It's the opposite. Most of this post's providers went out with some kind of bang: a scam ring with twenty coordinated brands, a lawsuit and a midnight disappearance, a formal UK liquidation with a legal deadline attached. HT-Hosting went out so quietly that the community, a group of people whose entire hobby is watching for exactly this, who keep running deadpool-list threads specifically so nothing slips past them, took over a month to clock that it had already happened. There was no clustering of panicked posts, no gallows-humor roll call like the one that greeted HostDare, HostSolutions, and NexusBytes failing in the same stretch of weeks. Just silence, and then, eventually, someone noticing the silence.

The two review threads that predate the shutdown, "My HT-Hosting review" and "HT-Hosting.de is not a good provider," are worth reading as their own small genre. Neither one is about a single catastrophic failure, they're both about the accumulation of small, ordinary disappointments: tickets that took days instead of hours, uptime that never quite matched what was advertised, a support team that always seemed one step behind whatever had just broken. That's a different kind of warning sign than the dramatic ones elsewhere in this post. It's not a red flag anyone can point to and say "there, that's the moment to leave." It's just a slow accumulation of "this isn't great," repeated often enough, by enough different people, that in hindsight it reads as an obvious pattern nobody quite acted on in time.

The ChatGPT-drafted apologies deserve their own mention, because they're a small, specific detail that says a lot about where HT-Hosting was by the end. A company that's still functioning normally doesn't need to lean on an AI tool to write an apology to its own customers. That's the kind of shortcut a business reaches for when it's already running thin on the time, staff, or plain motivation to write one itself. It wasn't a scandal. It was just one more small sign, alongside all the others, that nobody at HT-Hosting had much left to give.

Sometimes a company doesn't get a dramatic ending because it was never important enough to deserve one. HT-Hosting's reputation had been sinking for long enough, and its base of customers who still trusted it had shrunk small enough, that by the time it actually died there was almost nobody left paying close enough attention to notice right away. That's its own kind of ending, quieter and in some ways sadder than a scam or a lawsuit, a company that spent its last stretch of life disappointing the few people still willing to give it a chance, and then vanished without even the dignity of anyone immediately caring.

It's worth contrasting this with HostDare's death a few sections back, since the two happened in roughly the same era but landed completely differently on the community's radar. HostDare was diagnosed within hours by a forum full of people watching in real time. HT-Hosting took over a month to even register as dead, because by the time it actually stopped, most of the people who might have noticed had already quietly stopped paying attention to it. Reputation, it turns out, isn't just about whether a company survives. It's about whether anyone's still watching closely enough to notice when it doesn't.

There's a version of this story that's almost comforting, in a backhanded way: HT-Hosting's death caused less damage than it might have precisely because so few people were still relying on it by the end. The customers who left after the hacking incident, or after one too many rounds of downtime, weren't around to lose anything when the final shutdown came. In a strange sense, the company's declining reputation did some of the protective work a warning label normally would.

Reading the warning signs in real time

Every case in this post so far is a finished story, the company died, and the forum wrote its history afterward. HostSlick is different: a provider the community has been watching, in real time, slide toward a deadpool that may or may not have technically arrived by the time you're reading this. Over roughly three years, from 2023 into 2026, HostSlick has accumulated a pattern too consistent to be bad luck: servers down for days at a stretch with no ticket response, customers discovering after the fact that they'd been hacked with no notification from the company, VPS instances quietly vanishing from customer control panels, a cryptocurrency refund on a USDT/TRC20 payment stonewalled for months while communication went dark entirely.

The thread titles alone tell the story in sequence: "HostSlick being shady" in the earlier days, then "HostSlick order cancelled, no refund for 45 days," then "HostSlick service down 2 weeks," then a direct "SCAM ALERT: HostSlick.com," and finally "Yet another complaint about HostSlick, please respect each other", that last title a small, telling sign of a community starting to argue among itself about how much pile-on is fair for a company that hasn't technically died yet. One customer's account was reportedly deleted from the site along with the evidence of their dispute, the money never returned, according to a summary of the thread, the kind of detail that, if confirmed, moves HostSlick out of "struggling provider" territory and into something closer to what the twenty-brand scam ring was doing, just slower and less coordinated.

None of these incidents alone would be unusual for a struggling host having a bad quarter, outages happen, refund processing gets backed up, security incidents occur even at well-run companies. Stacked together, over years, repeated across multiple independent customers with no sign of the pattern improving, they're something the forum has started calling exactly what it looks like: "a deadpool waiting to happen." That phrase shows up unprompted across several of the threads, different users independently reaching for the same conclusion without coordinating with each other first.

That last thread title, "Yet another complaint about HostSlick, please respect each other", is worth pausing on, because it shows the community arguing with itself about something none of the earlier cases in this post raised: how much criticism is fair to level at a company that's still, technically, in business. Pile-on threads can tip into something closer to a mob than a warning system, and regulars who've watched that happen before sometimes step in to slow it down, even when the underlying complaints are legitimate. It's a genuinely hard line to walk, protecting future customers from a real pattern of harm without turning a public forum into a place where a struggling company gets talked into an early grave by its own critics.

Outages in February and again in April, the deleted-account allegation, the stonewalled crypto refund, none of these were reported by the same customer, which is part of what makes the pattern so hard to dismiss. A single angry customer with one bad experience is a data point. Half a dozen unrelated customers, over three years, independently describing variations on the same failures, no ticket response, no notification after a breach, no refund after a cancellation, is closer to a trend, and trends are exactly what a "deadpool waiting to happen" thread exists to document while it's still forming.

This is the case worth paying closest attention to in this whole post, because it shows the community doing the thing all of this is really about, not mourning a death after the fact, but diagnosing one while it's still happening, thread by thread, complaint by complaint, in public, where the next customer can find it before they hand over a payment. Someone new considering HostSlick today doesn't have to guess. They can read years of documented outages, unanswered tickets, and stonewalled refunds and draw the obvious conclusion months or years before any final shutdown notice, if one ever comes at all. That's the whole value of the forum's habit of keeping receipts: it turns hindsight into foresight for the next customer, assuming the next customer bothers to look before they buy.

There's also a genuine possibility that HostSlick never technically deadpools at all, that it just keeps operating in this degraded, complaint-generating state indefinitely, profitable enough to survive, disappointing enough that nobody would call it healthy. That outcome doesn't fit neatly into any other section in this post, and it might be the most common outcome of all for providers like this, simply because it never produces a single dramatic event worth writing a section about. Most struggling companies don't die cleanly. They just get worse, slowly, for long enough that eventually almost nobody remembers when things were still good.

Whichever way it eventually resolves, this section is deliberately left open rather than tied off, because that's the honest state of the evidence at the time this post was written. A published post is a snapshot, not a live feed, and HostSlick is the one case here where the snapshot might already be out of date by the time a reader gets to it, which is itself a small lesson about how quickly the ground can shift under a story like this one.

The night the servers left the building

Most deadpools happen in email inboxes and support tickets. This one, from August 2013, happened at a loading dock in Florida in the middle of the night, and it's the oldest, strangest, and most physically dramatic case in this post. VolumeDrive ran roughly a thousand servers, priced aggressively below what it likely cost to run them, and had racked up serious debt with its own upstream infrastructure supplier, BurstNET, while separately falling behind on payments at a Florida data center that was hosting a large share of its hardware.

According to accounts from people involved at the time, VolumeDrive's own staff showed up at that Florida facility overnight and physically removed hardware the company no longer had any legal right to touch, then disappeared. A financing and leasing company, which had supplied VolumeDrive with equipment under a lease arrangement rather than an outright sale, later said it was owed $116,000 and that 182 leased servers were being held illegally, hardware VolumeDrive had taken possession of but never actually owned, moved out under cover of darkness rather than surrendered back to its rightful owner. Everything, the website, the servers, the phone line, went dark at the same time for the customers still depending on that Florida capacity. The colocation provider left holding the mess later described the whole exit in three blunt words: the company had "dined and dashed."

This is the one case in the post that crossed all the way from forum lore into an actual courtroom. A leasing company, Data Sales Co., Inc., filed suit against VolumeDrive on October 23, 2013, alleging breach of fiduciary duty, meaning there's a real legal record behind the forum posts on lowendtalk.com, not just secondhand recollection filtered through years of retelling. The lawsuit, and the underlying facts it alleged, turned what could have been dismissed as exaggerated forum drama into something with actual documentary weight: invoices dating back to January 2013, a specific dollar figure, a specific count of servers, a specific legal theory about who owed what to whom.

The leasing arrangement at the center of this story is worth explaining, because it's a financing pattern that shows up quietly across the hosting industry and rarely gets discussed outside a story like this one. Buying a thousand physical servers outright is expensive, so hosting companies frequently lease hardware instead, paying a financing company for the right to use equipment the financing company still legally owns, the same basic structure as leasing a car. That arrangement works fine as long as the lease payments keep flowing. The moment they don't, the hardware isn't really the host's to keep, move, or hide, no matter how badly a company in financial trouble might want it to be.

That's exactly the gap VolumeDrive fell into. The company had taken possession of 182 servers under a lease it had stopped paying, and rather than surrendering that hardware back to the financing company it owed, it apparently moved the equipment out of the Florida facility under cover of night, not a repossession the company resisted, but an active choice to relocate assets it no longer had a legal claim to. That's the detail that turns a financial collapse into something closer to theft, and it's the detail Data Sales Co.'s lawsuit was built around.

It didn't happen instantly, either. VolumeDrive apparently kept limping along afterward for some customers rather than vanishing in one clean stroke, continuing to serve at least part of its customer base even as the Florida situation was unraveling behind the scenes, which makes this less a single midnight event and more a slow-motion collapse with one unmistakably criminal-looking scene in the middle of it. Threads on lowendtalk.com tracked it across months: "VolumeDrive may have deadpooled" as an early, uncertain question, followed later by "VolumeDrive being sued" once the Data Sales Co. filing became public, and "VolumeDrive disappointed" capturing the flatter, more exhausted tone of customers who'd simply stopped expecting anything better by that point.

Selling servers "below what it likely cost to run them" is its own quiet warning sign, one that shows up in more than one case in this post. A hosting company operating at a genuine loss on every customer isn't building a sustainable business. It's borrowing against the future, whether that borrowing takes the shape of unpaid upstream bills, unfunded lease obligations, or simply a founder's day job covering the gap. VolumeDrive's collapse looks dramatic because of the midnight hardware run, but the underlying arithmetic, revenue that never covered real costs, is the same quiet failure mode that eventually caught up with MyW, with NexusBytes, and in a slower, gentler way, with DataIdeas too.

Being the oldest case in this post also means VolumeDrive predates most of the community infrastructure that makes the later sections possible to document as thoroughly as they are. There's no LES thread with quoted usernames here, no LowEndBox retrospective written with the benefit of hindsight, just older LET threads, thinner search coverage, and a lawsuit that happened to survive in public records long after the forum posts describing it could have quietly faded from memory.