BlueVM Review - Definitely NOT Recommended - AVOID BlueVM!
IMPORTANT NOTE: I recently canceled my BlueVM VPS and gave the BlueVM credit to another LET member. At the same time, I promised to create a new thread with a review of my experience with BlueVM. Someone else opened their own somewhat positive review of BlueVM shortly thereafter. I will not say that it was an attempt to preempt my pending negative review. Nonetheless, I decided to start my own thread as originally promised, to make sure that it began with a clearly negative review of BlueVM. Read below to see why. See also:
HERE IS MY REVIEW:
Don't be tempted by the value of their offers - you will regret it. They will never refund money to customers, even if your BlueVM VPS is down for a month and it is entirely BlueVM's failure to deliver the VPS you paid for. (They will offer BlueVM credit for BlueVM services, but who wants that after a month long ongoing service failure?) Buyer beware!
My BlueVM KVM VPS went down a month ago. It took a week for BlueVM to bring it up at all. It is still unusable several weeks later.
The node drops all communications for two minute intervals several times an hour. The communications dropouts continue to this day, with no end in sight. Every VPS on that node is affected. There are no inbound or outbound communications at all. Even BlueVM's own Feathur control panel times out trying to connect to the node/VPS. Imagine what it is like for your VPS to lose all network communications (outbound, too!) several times an hour.
WATCH BLUEVM DROP ALL YOUR PACKETS! YOU CAN SEE IT FOR YOURSELF RIGHT NOW!
Type "ping zu2.bluevm.com" (Windows: "ping -t zu2.bluevm.com") and watch for a few minutes (20 minutes or less). On Mac or Windows you will see the Request timeout messages. On Linux, just watch the icmp_req number suddenly stop incrementing or jump when the node does not respond.
Did I open a ticket? Sure. Did they respond? Yes, although response times often took longer than they should. BlueVM told me that they had fixed the problem four different times in the same ticket, but the same problem continues.
Here is my summary of BlueVM responses edited for brevity. I omitted irrelevant and automated messages.
- 25 June (me): I opened ticket number 985117 about frequent communications dropouts.
- 25 June (BlueVM): We're aware.
- 1 July (BlueVM): Fixed.
- 1 July (me): Not fixed. Nothing has changed. I included detailed instructions showing many ways to see the issue.
1 July (BlueVM): Fixed (again).
2 July (me): Not fixed. Another outage is occurring now.
- 2 July (BlueVM): We're now aware that there is still a problem.
- 2 July (BlueVM follow-up): Working with the DC on the problem.
- 6 July (BlueVM): This is resolved now.
- 10 July (me) I was busy, but on 10 July, I notified them that dropouts continued. How could they NOT notice?
- 10 July (BlueVM): Offers to move me to a different node or cancel my VPS and give me credit from BlueVM. They will not credit my PayPal account. I declined both - I wanted a VPS outside the US, and what could I possibly do with a credit from BlueVM??
- 11 July (BlueVM): We believe the DC has fixed it.
- (12 July: I told them that the problem continues. Again, how could they not know?)
13 July: Ok. We will continue to work with the DC to fix this.
13 July: I opened a new ticket, asking them to cancel my VPS and apply the credit to another BlueVM customer that I found on LET.
Summary: BlueVM's Zurich KVM node (zu2.bluevm.com) has been unusable for a month. All communications fail for every VPS on that node several times an hour. It is trivial for anyone to see (whether or not you are BlueVM customer) by simply pinging the node. In one ticket alone, BlueVM claims to have fixed the problem many times, yet it still continues, with no end in sight. In the time it took to type this message, I saw multiple communications dropouts occur.
I could provide many more examples of why I do not recommend BlueVM, but I believe the above information is sufficient. Do not give them your money.