@jcn50 said:
Above the price chitchat I think there is a real priority problem in VirmAche's head, and a disrespect to its "users" (I won't say "customers" anymore because there is no such relationship defacto, the server is still offline after 4 days and not a single word from the man).
It is not a hosting "business", it's a gambling endeavor, no wonder https://vps.blackfriday looks like a casino website from Las Vegas - take your bets, play crap. Grab a server, and you might not get an IP, rDNS/PTR, warranty, support, replacement, uptime, CPU, RAM, disk... you can lose it all at any moment. Port 25/80/443? Optional! Custom ISO? You really believe in Santa, aren't you.
Yeah, the man is busy: we all are.
I'm always surprised when someone here buys a VirMach server and doesn't understand what they signed up for, I figured by now anyone here knew exactly what they were getting. Timetables are flexible at best, communication can be sporadic, but the prices are great and he's always made up for issues in the end. If you need a production server this probably isn't it, you can pay production prices and get what you're expecting, my production dedicated server costs literally twice as much with less specs.
@bakageta said:
I'm always surprised when someone here buys a VirMach server and doesn't understand what they signed up for, I figured by now anyone here knew exactly what they were getting.
It's a big assumption to think that people were on LES before they bought their service. I only found out about LES after a year of downtime and lack of communication on tickets for that entire time. After a LOT of searching, I found this on LES.
Also, I am always surprised when OG and longtime LES members are surprised when "VirMach - Complain - Moan - Praise - Chit Chat" actually contains complaints and moans. Are they all fan boys or something?
I personally have reconciled my expectations based on my "need" now, but it is entirely normal to feel that something should work, and it is annoying to see how people are talked down to when they first come in here frustrated by lack of ticket response. Downtime is NOT a normal expectation and getting beat down for expecting something to work is also not normal. There are degrees of not meeting expectation that are up for discussion, but frankly, extended downtime w/o communication is never an acceptable business model (and yes, I mean never). For all I "get" about @VirMach and great intentions, this is one thing that needs MUCH work. We don't need encyclopedia article communication. We need prompt communication regardless whether the fix is prompt. The SLA should address this by mentioning reasonable time of response to tickets if extended lack of communication is what a buyer should expect.
@Brayvin said: It's a big assumption to think that people were on LES before they bought their service. I only found out about LES after a year of downtime and lack of communication on tickets for that entire time. After a LOT of searching, I found this on LES.
They joined in 2020. Their situation is different from yours. ;-)
@Brayvin said: Downtime is NOT a normal expectation and getting beat down for expecting something to work is also not normal. There are degrees of not meeting expectation that are up for discussion, but frankly, extended downtime w/o communication is never an acceptable business model (and yes, I mean never).
I don't think @bakageta was beating anybody down. As for your second statement, your opinions are your own and that cool. I'm a believer that any absolute like that is false. There's always an exception.
@Brayvin said: Downtime is NOT a normal expectation and getting beat down for expecting something to work is also not normal. There are degrees of not meeting expectation that are up for discussion, but frankly, extended downtime w/o communication is never an acceptable business model (and yes, I mean never).
I don't think @bakageta was beating anybody down. As for your second statement, your opinions are your own and that cool. I'm a believer that any absolute like that is false. There's always an exception.
Which is why I mentioned the SLA making such "exceptions" known.
@Brayvin said: Downtime is NOT a normal expectation and getting beat down for expecting something to work is also not normal. There are degrees of not meeting expectation that are up for discussion, but frankly, extended downtime w/o communication is never an acceptable business model (and yes, I mean never).
I don't think @bakageta was beating anybody down. As for your second statement, your opinions are your own and that cool. I'm a believer that any absolute like that is false. There's always an exception.
Which is why I mentioned the SLA making such "exceptions" known.
So your statement should have read "extended downtime w/o communication is never an acceptable business model (and yes, I mean never unless it's in the SLA)"?
@Brayvin said:
It's a big assumption to think that people were on LES before they bought their service. I only found out about LES after a year of downtime and lack of communication on tickets for that entire time. After a LOT of searching, I found this on LES.
Also, I am always surprised when OG and longtime LES members are surprised when "VirMach - Complain - Moan - Praise - Chit Chat" actually contains complaints and moans. Are they all fan boys or something?
I mean, if you paid attention to who I was talking to (hint: it wasn't you) you'd see that they've been on the forum for half a decade. I've done my share of complaining here, and at OGF before, of course there's gonna be complaints here. If they've been on the forum longer than this thread existed, I don't really think they should be surprised by what they're buying.
Feel free to go back to complaining though, this is the place for it. I encourage you to actually look up reviews of the next service you buy though, there's plenty of low-end providers that you don't want to waste your time with.
@Brayvin said: Downtime is NOT a normal expectation and getting beat down for expecting something to work is also not normal. There are degrees of not meeting expectation that are up for discussion, but frankly, extended downtime w/o communication is never an acceptable business model (and yes, I mean never).
I don't think @bakageta was beating anybody down. As for your second statement, your opinions are your own and that cool. I'm a believer that any absolute like that is false. There's always an exception.
Which is why I mentioned the SLA making such "exceptions" known.
So your statement should have read "extended downtime w/o communication is never an acceptable business model (and yes, I mean never unless it's in the SLA)"?
SLA is communication, so, while your improvement is more helpful to some extent, I stand by "never" because "never" implies that the SLA does not communicate what to expect - i.e. running a business without adequate communication in this case is the SLA that doesn't expressly say you may have to wait days, weeks, or months for a response. I should not have to wade through a forum to determine that that is an expectation that I should have before making a purchase.
I am glad that @VirMach has changed the SLA to be more reflective of the actual conditions since the time I acquired my services, but the long periods of silence, having to come to a third-party site forum, still not having timely vendor responses, etc., are really, really frustrating for people trying to grasp why their stuff isn't working. He did really well for a while, but it looks like things are back in the bogs. I'm fortunate that my recent outages have been brief, but VirMach was definitely in violation of the original SLA I bought my services under when I eventually found this forum. "Timely" should be defined should be in some documentation, and not just in forum activity. Then, just point people to that and ask if they read it before they bought something instead of all this posturing and defending.
If its not clear, I am happy with my services at the moment and so this is not a complaint about my situation, but it is getting kind of old to see all the "its your own fault" when up-front communication/documentation does not set forth appropriate expectations to have. I'm not saying there can't be unfortunate lapses, etc., but when there are recurring issues, then probably one should own them and document them as unfortunately necessary to consider when making a purchase.
@Brayvin said: SLA is communication, so, while your improvement is more helpful to some extent, I stand by "never" because "never" implies that the SLA does not communicate what to expect - i.e. running a business without adequate communication in this case is the SLA that doesn't expressly say you may have to wait days, weeks, or months for a response. I should not have to wade through a forum to determine that that is an expectation that I should have before making a purchase.
I can see your point. I don't read your statement that way but can see how you might. To me your statement reads present tense ( this outage has happened you should alert me now ) rather than past tense ( this outage has happened but at least I am aware this could happen ).
I've never read the SLA. What does it say is the repercussion of violating the SLA?
@Brayvin said: If its not clear, I am happy with my services at the moment and so this is not a complaint about my situation, but it is getting kind of old to see all the "its your own fault" when up-front communication/documentation does not set forth appropriate expectations to have. I'm not saying there can't be unfortunate lapses, etc., but when there are recurring issues, then probably one should own them and document them as unfortunately necessary to consider when making a purchase.
And this I agree with ( and for which reason I disqualified our OP ) though I'd say an SLA is only a portion of due diligence when vetting a provider.
@Brayvin said:
Also, I am always surprised when OG and longtime LES members are surprised when "VirMach - Complain - Moan - Praise - Chit Chat" actually contains complaints and moans. Are they all fan boys or something?
Not a fanboy - never bought any of his products. I’m just here to poke fun at the ones who have. Always easier to kick people while they’re down, right?
Jokes aside, "OG" are the folks who’ve been here since page 1 of this nearly 400-page saga. We’ve seen it all and grown immune to it after hearing the same complaints for years: downtime, uptime, dead nodes, migrations, lost data, rinse and repeat.
So yeah, we find it a bit entertaining when people still jump in “because it’s cheap” without doing basic due diligence. A simple Google search for "virmach review" says plenty: https://www.google.com/search?q=virmach+review
Of course, you’re free to think and do whatever you like—and so are we. Some of us just enjoy playing devil’s advocate here… because honestly, it’s fun.
Never make the same mistake twice. There are so many new ones to make.
It’s OK if you disagree with me. I can’t force you to be right.
@tulipyun said:
Are all nodes in San Jose offline, or only specific nodes (e.g., SJCZ012)?
same question here!!!!!!
I also want to know how to open a ticket?
Running diagnostics...
Main Server IP: Offline
Node Server: Offline
Service Status: Active
Conclusion: Both your server and node appear to be offline. Please check the network status page for updates.
If you cannot make a ticket due to troubleshooter timing out, go back and click Network Status.
@somik said: but @VirMach probably needs to look into having something like a twitter account or a blog where he updates whats down and what is being done.
@somik said: but @VirMach probably needs to look into having something like a twitter account or a blog where he updates whats down and what is being done.
@cornercase said: SJCZC005B is missing from the status page (and also down).
So at least 7x servers down in total @ the same location.... that's terrible... & still no words from the man. He'll probably post 3 pages of explanations about trips to data centers when he comes back (in a month or so) all without a "sorry". Meanwhile: he already started to code a Halloween Pumpkin Wheel~ and a Fireworks Pop Pop Bang Lucky Box for the New Year [=priorities completely messed up]. For Summer 2026: it will be a Blow Up My Coconuts sale. It's so nice to plan useful stuff ahead!
Comments
I'm always surprised when someone here buys a VirMach server and doesn't understand what they signed up for, I figured by now anyone here knew exactly what they were getting. Timetables are flexible at best, communication can be sporadic, but the prices are great and he's always made up for issues in the end. If you need a production server this probably isn't it, you can pay production prices and get what you're expecting, my production dedicated server costs literally twice as much with less specs.
It's a big assumption to think that people were on LES before they bought their service. I only found out about LES after a year of downtime and lack of communication on tickets for that entire time. After a LOT of searching, I found this on LES.
Also, I am always surprised when OG and longtime LES members are surprised when "VirMach - Complain - Moan - Praise - Chit Chat" actually contains complaints and moans. Are they all fan boys or something?
I personally have reconciled my expectations based on my "need" now, but it is entirely normal to feel that something should work, and it is annoying to see how people are talked down to when they first come in here frustrated by lack of ticket response. Downtime is NOT a normal expectation and getting beat down for expecting something to work is also not normal. There are degrees of not meeting expectation that are up for discussion, but frankly, extended downtime w/o communication is never an acceptable business model (and yes, I mean never). For all I "get" about @VirMach and great intentions, this is one thing that needs MUCH work. We don't need encyclopedia article communication. We need prompt communication regardless whether the fix is prompt. The SLA should address this by mentioning reasonable time of response to tickets if extended lack of communication is what a buyer should expect.
They joined in 2020. Their situation is different from yours. ;-)
I don't think @bakageta was beating anybody down. As for your second statement, your opinions are your own and that cool. I'm a believer that any absolute like that is false. There's always an exception.
Which is why I mentioned the SLA making such "exceptions" known.
So your statement should have read "extended downtime w/o communication is never an acceptable business model (and yes, I mean never unless it's in the SLA)"?
I mean, if you paid attention to who I was talking to (hint: it wasn't you) you'd see that they've been on the forum for half a decade. I've done my share of complaining here, and at OGF before, of course there's gonna be complaints here. If they've been on the forum longer than this thread existed, I don't really think they should be surprised by what they're buying.
Feel free to go back to complaining though, this is the place for it. I encourage you to actually look up reviews of the next service you buy though, there's plenty of low-end providers that you don't want to waste your time with.
SLA is communication, so, while your improvement is more helpful to some extent, I stand by "never" because "never" implies that the SLA does not communicate what to expect - i.e. running a business without adequate communication in this case is the SLA that doesn't expressly say you may have to wait days, weeks, or months for a response. I should not have to wade through a forum to determine that that is an expectation that I should have before making a purchase.
I am glad that @VirMach has changed the SLA to be more reflective of the actual conditions since the time I acquired my services, but the long periods of silence, having to come to a third-party site forum, still not having timely vendor responses, etc., are really, really frustrating for people trying to grasp why their stuff isn't working. He did really well for a while, but it looks like things are back in the bogs. I'm fortunate that my recent outages have been brief, but VirMach was definitely in violation of the original SLA I bought my services under when I eventually found this forum. "Timely" should be defined should be in some documentation, and not just in forum activity. Then, just point people to that and ask if they read it before they bought something instead of all this posturing and defending.
If its not clear, I am happy with my services at the moment and so this is not a complaint about my situation, but it is getting kind of old to see all the "its your own fault" when up-front communication/documentation does not set forth appropriate expectations to have. I'm not saying there can't be unfortunate lapses, etc., but when there are recurring issues, then probably one should own them and document them as unfortunately necessary to consider when making a purchase.
I can see your point. I don't read your statement that way but can see how you might. To me your statement reads present tense ( this outage has happened you should alert me now ) rather than past tense ( this outage has happened but at least I am aware this could happen ).
I've never read the SLA. What does it say is the repercussion of violating the SLA?
And this I agree with ( and for which reason I disqualified our OP ) though I'd say an SLA is only a portion of due diligence when vetting a provider.
Looks like SJC just died
Yup; had been a lot of Load spikes earlier.
In other news: "https://status.virm.ac/ might have a temporary problem or .."
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Y'all upset 'im and he's gone on a sabbatical to Trinidad, or somethin'.
[Edit] Status is back
OKL inbound fault and SJC (aka CHIZ001) inaccessible.
[Edit2] I'm starting a collection
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
It seems everything in San Jose is off.
Not a fanboy - never bought any of his products. I’m just here to poke fun at the ones who have. Always easier to kick people while they’re down, right?
Jokes aside, "OG" are the folks who’ve been here since page 1 of this nearly 400-page saga. We’ve seen it all and grown immune to it after hearing the same complaints for years: downtime, uptime, dead nodes, migrations, lost data, rinse and repeat.
So yeah, we find it a bit entertaining when people still jump in “because it’s cheap” without doing basic due diligence. A simple Google search for "virmach review" says plenty: https://www.google.com/search?q=virmach+review
Of course, you’re free to think and do whatever you like—and so are we. Some of us just enjoy playing devil’s advocate here… because honestly, it’s fun.
Never make the same mistake twice. There are so many new ones to make.
It’s OK if you disagree with me. I can’t force you to be right.
It seems that it's too difficult for some to read just a few posts above, before they post!
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Are all nodes in San Jose offline, or only specific nodes (e.g., SJCZ012)?
same question here!!!!!!
I also want to know how to open a ticket?
Running diagnostics...
Main Server IP: Offline
Node Server: Offline
Service Status: Active
Conclusion: Both your server and node appear to be offline. Please check the network status page for updates.
If you cannot make a ticket due to troubleshooter timing out, go back and click Network Status.
I am on three separate servers and all are down in SJC.
Time to restore backups
I now have another server down
SJCZ006since 5 hours ago:https://status.virm.ac/?s=62498bf5e694aa34355ded37
All the 6x servers at the same location are down:
How much are you losing per hour?
He has one but it's not used since 2023:
https://x.com/virmachcloud
There is this status page but it is working 1 time out of 10 and some servers aren't even listed:
https://status.virm.ac/
He connects/comes here every day... but does not post (probably because the state of affairs isn't progressing).
Tickets are useless anyway my friend~
Will @FrankZ return?
Will servers be back online?
Everything is possible.
The status page is useless. You already know your server is down. Dont need another thing to tell you the same.
He should probably start updating his twitter (or X if you prefer)...
Good eye! I just checked as well and he was online 1.5 hours ago (from this message)
Either he is alive or someone else is using his account
Never make the same mistake twice. There are so many new ones to make.
It’s OK if you disagree with me. I can’t force you to be right.
1,000 VND per hour!
SJCZC005B is missing from the status page (and also down).
So at least 7x servers down in total @ the same location.... that's terrible... & still no words from the man. He'll probably post 3 pages of explanations about trips to data centers when he comes back (in a month or so) all without a "sorry". Meanwhile: he already started to code a Halloween Pumpkin Wheel~ and a Fireworks Pop Pop Bang Lucky Box for the New Year [=priorities completely messed up]. For Summer 2026: it will be a Blow Up My Coconuts sale. It's so nice to plan useful stuff ahead!
50 new posts, not a single VirMach post. I hope you have fun talking among yourselves
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
You want more?