All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
ServerHost / VPSHostingService.co (Server Host) / (VPS Hosting Service) wiped my VPS and changed IP
My VPS disappeared and was apparently reprovisioned — support initially denied making any changes
I woke up on August 21 to find that one of my VPS instances at ServerHost / VPSHostingService.co was effectively gone.
This wasn’t a crashed service or a broken network configuration. The server that had been at 107.173.229.139 was now at 107.175.114.68, the previous password no longer worked, and when I finally gained access, my data and environment were gone.
It appeared to be a newly provisioned VPS.
I immediately opened a support ticket. Their first response was:
“We did not make any changes inside your VPS, including the network configuration, files, or data. Nothing was modified from our side inside the VPS.”
The problem is that their own Virtualizor control panel appears to contradict that explanation.
The Tasks and Logs page for VPSID 60620 shows, on August 21:
2:43 PM — Create VPS Operation
2:44 PM — Installing Guest Agent
2:44 PM — VPS Start
All three operations show as completed.
That is not something occurring “inside” my VPS. Those are control-plane provisioning operations on the hosting platform itself.
I pointed this out and provided a screenshot. I also explained that the original IP had always been 107.173.229.139 and that 107.175.114.68 was new. Support subsequently said the ticket had been forwarded to the appropriate team for investigation.
More than 14 hours later, I was still waiting for an explanation.
I have backups, so this isn’t simply about whether I can rebuild the machine. Restoring the application is itself work because the replacement VPS needs its dependencies rebuilt, and I still need to recover one backend .env file.
More importantly, I don’t want to restore a production backup onto the mystery VPS until ServerHost explains what happened. Doing so would alter the machine and potentially muddy the evidence. And since I have two other VPS instances with this company, I need to know whether their data is actually safe before trusting this infrastructure again.
Servers can fail. Hardware can fail. Automation can fail. People can make mistakes. I understand all of that.
What destroys confidence is having a VPS apparently reprovisioned, seeing a “Create VPS Operation” in the provider’s own management logs, and initially being told that nothing was changed from their side.
I am giving ServerHost / VPS Hosting Service an opportunity to investigate and provide a technical explanation. If they determine what happened and handle it appropriately, I will update this review accordingly.
Until then, I cannot recommend putting important workloads on their infrastructure without maintaining independent off-provider backups.
Screenshot of the provider’s Virtualizor task log retained as evidence.
Comments
I feel your response is fair.
It has been less then a day, so providing them an opportunity to investigate and resolve which could take several days depending on severity is reasonable.
I would expect an update within the first 24 hour window, since silence indicates a possible problem which the customer should be aware of.
Thanks for the heads up. I bought a VPS from them last month and am curious to hear how they respond.
Yes, but I believe the initial push back from them was unwarranted.
I agree, it was an oversight to ping that reply back without further checks by them. That indicates they did not take your ticket seriously.