Earlier this month, I signed up with VPS.net for their VPS cloud service after reading a few good things about them from some famous bloggers and the on the WebHostingTalk forum. I chose 4 nodes on their SLC-F cloud that gave me 2.4GHz CPU, 1504 MB RAM and 40 GB disk space. I chose 4 nodes because it was more in line with the resources I had on my dedicated server with another provider. The ideas was to add more nodes when I needed it, it’s a cloud after all. The signing up was easy, but then I received this email from them :
Thank you for signing up for VPS.NET. Due to VPS.NET’s instant activations and scalability, we’re the subject of much credit card fraud. Because of this, we have had to enforce stricter guidelines on clients matching certain criteria.
Unfortunately your account meets that criteria. We are eager to get you signed up and started on the VPS.NET cloud.
In order to activate your account, we will have to ask that you provide a faxed or scanned copy of your State or Government ID as well as Credit Card used. The names on these must match in order to activate your account.
Understandable. They wanted to make sure that I had not stolen someone else’s credit card. I got it sorted out and the hold on my account was removed. After that, I was able to quickly set everything up – wordpress, CPanel, DNS etc. and I moved all my sites from my previous host to the VPS.net server.
Everything seemed fine for the first 3 days or so, and then on the fourth day I started receiving alerts from Pingdom that my sites were down (If you are not using Pingdom, you should at least try their free service). I ignored the first few alerts thinking it might just be a blip. The issue did not get resolved till evening and that’s when I created a ticket with their support. I immediately received a canned reply stating that my issue will be looked into shortly. In about an hour, I received an update stating that there was a problem with SAN synchronization. Next day, my money sites were still down and leaking money. There were a few more updates on the ticket stating that the main issue has been fixed but that there was still some “slowness” in the synchronization. I thought Ok, this means my sites will be up soon. But NO, the server did not come back up even on Day 3. I asked them for an update and all I got was “We are working on this issue”. The worst thing was that they did not even have a support number that customers can call and talk to somebody. I searched their website and could not find one. I searched on WHT to see if anyone else was having issues with VPS.net and came across this thread. I was not alone – many were in the same boat as I. There was lots of mud slinging on that thread. Read it and you will get an idea.
Nothing changed on Day 4 and that’s when I decided enough is enough. Luckily, I had my old trusted dedicated server still running with my previous host. I immediately brought up all my sites on it (I lost about 2 days worth of updates and comments), but something is better than nothing. I then cancelled my account with VPS.net and asked them for a refund. The one good thing in this whole experience was that they immediately refunded my money and I did not have to worry about fighting another battle.
Overall, I would say stay away from VPS.net or at least their Salt Lake City clouds. It is definitely not worth all the trouble, especially if you have a few affiliate sites like me. Things may change in the future, but for now – No Thank you VPS.net!
If you have had any good or bad experiences with VPS.net, please share in the comments section for the benefit of others who may be looking for a reliable cloud hosting provider.