is Virmach perfect and 100% smooth all of the time? no (who is?)
are there sometimes some periods with great challenges on some servers? yes
is it a great idea to use a super cheap flash sale special for mission critical production? probably not
does most challenges and hickups get resolved and handled fairly? yes
do most VPS servers run extremely reliably most of the time? yes
is it most of the time the best value for money out there? yes
do I feel he does his best and has good and honest intentions? yes
do I trust and respect Virmach? absolutely yes
So depending on your criteria for "legit", I'd say, yes.
is Virmach perfect and 100% smooth all of the time? no (who is?)
are there sometimes some periods with great challenges on some servers? yes
is it a great idea to use a super cheap flash sale special for mission critical production? probably not
does most challenges and hickups get resolved and handled fairly? yes
do most VPS servers run extremely reliably most of the time? yes
is it most of the time the best value for money out there? yes
do I feel he does his best and has good and honest intentions? yes
do I trust and respect Virmach? absolutely yes
So depending on your criteria for "legit", I'd say, yes.
Wait, I thought it was one big pleasure misson from a masochist.
I'd never use them, but I'd have given up long ago tbh so kudos for keeping going Virmache
is Virmach perfect and 100% smooth all of the time? no (who is?)
are there sometimes some periods with great challenges on some servers? yes
is it a great idea to use a super cheap flash sale special for mission critical production? probably not
does most challenges and hickups get resolved and handled fairly? yes
do most VPS servers run extremely reliably most of the time? yes
is it most of the time the best value for money out there? yes
do I feel he does his best and has good and honest intentions? yes
do I trust and respect Virmach? absolutely yes
So depending on your criteria for "legit", I'd say, yes.
@virmach Do you have the ability to add IPv6 in Amsterdam ?
If so, is there a one time fee I can pay to add IPv6 to a $20/year VM on AMSD026.
HE IPv6 tunnels are really just not working out very well in that location.
Just asking. not that big of a deal if you can't, or don't want to.
EDIT: Added website (https) monitor stats for today to show what I am seeing relative to IPv4 on same node and native IPv6 on my VPS at VirMach FrankZfort.
@nightcat said:
never mind, NO HK user will visit to AMS host.
I guess I could just totally forget using IPv6 and go IPv4 only, but what would @yoursunny think about that.
I might end up on one of those lists somewhere.
I'm not going anywhere near CF. Besides it is a three IPv4 VM so I also use it as a DNS server and an inbound only mail server. Similar issue with the IPv6 DNS and there is no IPv6 on the mail server because HE blocks port 25.
I'm not going anywhere near CF. Besides it is a three IPv4 VM so I also use it as a DNS server and an inbound only mail server. Similar issue with the IPv6 DNS and there is no IPv6 on the mail server because HE blocks port 25.
You are already on many lists and I keep adding you daily mwahahahahaha!
I'm not going anywhere near CF. Besides it is a three IPv4 VM so I also use it as a DNS server and an inbound only mail server. Similar issue with the IPv6 DNS and there is no IPv6 on the mail server because HE blocks port 25.
You are already on many lists and I keep adding you daily mwahahahahaha!
I can't speak to TYOC030, but my VM on TYOC007 is doing fine.
EDIT: 20 minutes later my VMs on both TYOC039 and TYOC007 are unavailable.
Looks like a network issue in Tokyo, as all Tokyo nodes show as not reporting for the last 22 minutes on the status page.
@rpollestad said:
Oof. Got a notice that my SJ dedicated server is going away. That sucks.
Are you just done offering dedicated servers or is it just that location and I can migrate?
It's been a decision we've considered for a while, I wish I would've done it sooner and provided a longer notice and it especially sucks that we're doing it to the people that stuck around for so long but I believe it'll be good for everyone. I don't feel comfortable having broken controls, no planned resolution for that to improve the controls, and it seems like everything is only going to regress from here so it's best to do something important and try to be proactive this time. And the way it works out it just ends up clashing with our workflow where we often have extreme delays on even providing support and we don't want that.
We would want to offer dedicated servers, no's not the time. It will be later when we can do servers ourselves, our own hardware, as originally intended. It's just not something that can be done right now. Most we can offer is a VPS/VDS replacement for anyone interested.
Oof, that's a painful one to read. I haven't received any messages about my dedicated server going away, and just got (and paid for) the invoice for another year on mine. I guess that's what I get for not reading the forum very often So, is that confirmation that my dedi is disappearing soon too, and if so, what can be done to get a refund on that invoice? I definitely don't need a couple hundred dollars of VPS credits.
I checked statusbot.virm.ac @VirMach LAX2Z019 online
but my VPS is offline, can't be used, and the description :
Operation Timed Out After 90001 Milliseconds With 0 Bytes Received
been offline for a few days
@vgood said:
I checked statusbot.virm.ac @VirMach LAX2Z019 online
but my VPS is offline, can't be used, and the description :
Operation Timed Out After 90001 Milliseconds With 0 Bytes Received
been offline for a few days
There has been no updates on this one, I'm not sure what is going on with LAX2Z019 these days.
@vgood said: LAX2Z019 nodes. I want to try migration but it can't, the Migrate menu doesn't show any options.
I'm also on that node in Los Angeles. The node is having issues for the last couple of days and there are no control panel options available at the moment. It is also on the Virmach status page, so he is aware.
08/13/2023 12:57 Last Updated 08/13/2023 12:58
We're investigating and attempting to resolve an outage on LAX2Z019.
Don't try to migrate until things are completely fixed or you might break your VM and have further issues.
New here, inquire about virmach's refugee plan
I've bought a virmach Tokyo's refugee server 2months ago.
It works perfectly in the first month, but when the time comes in August. it has been down for almost a month (Node has been locked ‘temporarily’)
I've opened a ticket, the operator seems noted the problem but not going to slove it. and then closed.
Does anyone know how long time will virmach took to repair the server or it just works for the first month?
@cybertech said:
i think Virmach is busy with the master server issue at the moment
Really..... anyone knows how much issues per day they will meet? hahaha
too many.
I think if they really wanna to slove the problem, it just take minutes
the comment for this refugee plan is "An rotational working"
Eg Tyoc 007 works for jan, feb mar
tyoc 0029 works for apr may jun.....
Maybe virmach can make a rotational monthly plan instead of a refugee ones
Both of these nodes are 99.9% uptime over last 6 months and the issues you're describing would only have affected a small fraction of customers, mostly related to spamming re-install requests as it was facing problems. TYOC029 was more complicated, definitely not "minutes" to resolve. I don't know what you believe we're doing this entire time.
@FrankZ said: @virmach, I expect that @Artemis may be on TYOC029 which has not shown an update on the status page for a while.
We've been getting lots of tickets about it as it usually goes for Tokyo and this was done purposefully in this case. We just have to treat that location differently, as every update would bring in a bunch of tickets asking follow-up questions and it was a complicated matter that we were trying to avoid doing forced migrations to Los Angeles for as a quicker solution. We essentially had to go through every VM affected one by one multiple times and maybe spend an hour on each of them and then in the end most of them needed to get loaded back in carefully from disaster recovery backups, and a ton of other issues I don't want to get into but essentially 80-85% of people were online this entire time so it's not as large of an issue as something like LAX2Z019.
We could've left controls unlocked during the time if it wasn't a guaranteed crash every 6 hours from button mashing.
The New York node 027 has been down for a few months without any activity. Is it possible to migrate it to another location? I suspect that the New York node 027 might be completely unresponsive and beyond recovery.
@cybertech said:
i think Virmach is busy with the master server issue at the moment
Really..... anyone knows how much issues per day they will meet? hahaha
too many.
I think if they really wanna to slove the problem, it just take minutes
the comment for this refugee plan is "An rotational working"
Eg Tyoc 007 works for jan, feb mar
tyoc 0029 works for apr may jun.....
Maybe virmach can make a rotational monthly plan instead of a refugee ones
Both of these nodes are 99.9% uptime over last 6 months and the issues you're describing would only have affected a small fraction of customers, mostly related to spamming re-install requests as it was facing problems. TYOC029 was more complicated, definitely not "minutes" to resolve. I don't know what you believe we're doing this entire time.
@FrankZ said: @virmach, I expect that @Artemis may be on TYOC029 which has not shown an update on the status page for a while.
We've been getting lots of tickets about it as it usually goes for Tokyo and this was done purposefully in this case. We just have to treat that location differently, as every update would bring in a bunch of tickets asking follow-up questions and it was a complicated matter that we were trying to avoid doing forced migrations to Los Angeles for as a quicker solution. We essentially had to go through every VM affected one by one multiple times and maybe spend an hour on each of them and then in the end most of them needed to get loaded back in carefully from disaster recovery backups, and a ton of other issues I don't want to get into but essentially 80-85% of people were online this entire time so it's not as large of an issue as something like LAX2Z019.
We could've left controls unlocked during the time if it wasn't a guaranteed crash every 6 hours from button mashing.
Apologize for my word and thank you for your hard working..
As my experience , the VM works perfectly just in the first month.
And my friend's other virmach machine mostly work 99% like you say.
But mine has been down for about 1 month.
I understand it is a refugee plan, and you are not the UN High Commissioner for Refugees
Just hope it can online quickly.
I didn't login to the billing portal for a long time,
Then recently when I tried to use the ticketing system, I feel that maybe your side get a lot of stress from some abusers through ticketing system, so I don't want to disturb you there.
If you have time, may I ask could you please help to make IPv6 working on Tokyo node?
@XXSL said:
If you have time, may I ask could you please help to make IPv6 working on Tokyo node?
There is no IPv6 for Tokyo, there is no IPv6 support at all. It was there in semi-deploy state, now it's totally not supported, don't ask, dont expect it to work.
I think maybe they started to lose patience and feel angry (I can feel that through the page design of ticketing system ) for the abusers (and as this kinds of situation passing, even normal users) buying Tokyo node while getting more and more stress from ticketing system, so they lose the motivation for improving product there.
What I can recommend is why not make the price a little bit higher and kick all the stupid abusers away to have a fresh and nice daily mood.
I've gone through and overhauled our code for a lot of the stuff we've mentioned in the past to refine it and make sure it all works better in edge cases. The updates being pushed out over the weekend. This should mean the controls correctly break if an issue is detected related to a disk overloading, everything generally performing more uniformly, and more scenarios accounted for automatically when it comes to these issues. It's still not the version 2.0 we wanted to do on it all but it's an improvement.
Hivelocity has decided to vaguely and without notice disable ports on Chicago2 and Tampa, which we contacted them about today shortly after they were disabled. They said it might be a billing issue, turned on ports, sent it to billing department, and the billing department brought down the ports again and also brought it down for LAX2, citing abuse issues.
They're completely incapable of properly using their own systems, instead for some reason deciding to open tickets on multiple systems, then not correctly marking it as resolved on all systems. More recently it looks like they decided to use their LEGACY ticket system, which sends us 0 emails, and is hidden away, to open copies of old abuse reports that were already handled, plus a few new ones. They sent us an email directly about some of these, which I responded to multiple weeks ago and they ignored. This is where I explained these issues to them of them sending it over and over and it already being resolved for the ones they contacted us about at the time. Keep in mind none of these threats were active and most were handled already such a long time ago that no service even existed, others were already in a suspended state. In any case these were only about a 12 reported cases of abuse over a period of three months (out of multiple thousand IPv4 addresses.) They could've nullrouted the IP addresses as they always mention they'll do or which they do before they even send us the report in the past, yet someone in this company had to go through all this and decide it was a good decision to disable ports with no notice, to the point where even internally the network engineer assisting us had no idea what was going on and for some reason the billing department had to step in to figure out what was going on, only to disable ports again and then ignore our response so far.
Anyway, just making this comment so you guys realize how insane the situation is in case you're wondering what happened today. Let's see how they proceed after I went down and let them know of this again. I don't want you thinking this was our doing.
For reference, the only way for us to have been able to see these reports would have been to click this button, which is supposed to be old tickets from several months ago only. No email because the legacy system is not used for communication.
@yoursunny said:
It's time to cancel Hivelocity and move everything to xTom.
They're also refusing to allow us to come pick up our equipment it seems until it's been reviewed by someone else. I don't even want to pretend to understand in what way that's related to the abuse issue described above, assuming any of it was even valid, like there's going to be phantom abuse that occurs after we pick up our equipment and have it hosted elsewhere? What's their end goal? To leave absolutely no level of trust left?
It's so sad that all the talented individuals that work there are essentially turned into paperweights until the people that caused the problems come back in the next day to remove the excessive red tape. And of course once they do show up, we already know they will be incapable of showing any remorse or taking any responsibility, they're only experts at getting defensive and shifting blame.
Comments
is virmach legit?
No.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
is Virmach perfect and 100% smooth all of the time? no (who is?)
are there sometimes some periods with great challenges on some servers? yes
is it a great idea to use a super cheap flash sale special for mission critical production? probably not
does most challenges and hickups get resolved and handled fairly? yes
do most VPS servers run extremely reliably most of the time? yes
is it most of the time the best value for money out there? yes
do I feel he does his best and has good and honest intentions? yes
do I trust and respect Virmach? absolutely yes
So depending on your criteria for "legit", I'd say, yes.
well said, could not say it any better.
Wait, I thought it was one big pleasure misson from a masochist.
I'd never use them, but I'd have given up long ago tbh so kudos for keeping going Virmache
thanks for yours insight
I moved the site out of the NJ node a long time ago, and I guess it was a smart move, at least for now it's stable.
TYOC007 offline?
yes, it appears so.
EDIT: Back online as of ~7 hours ago.
@virmach Do you have the ability to add IPv6 in Amsterdam ?
If so, is there a one time fee I can pay to add IPv6 to a $20/year VM on AMSD026.
HE IPv6 tunnels are really just not working out very well in that location.
Just asking. not that big of a deal if you can't, or don't want to.
EDIT: Added website (https) monitor stats for today to show what I am seeing relative to IPv4 on same node and native IPv6 on my VPS at VirMach FrankZfort.
Amsterdam node: AMSD026 IPv4
Amsterdam node: AMSD026 with HE tunnel IPv6
Frankfurt node FFME006 with native IPv6
never mind, NO HK user will visit to AMS host.
I guess I could just totally forget using IPv6 and go IPv4 only, but what would @yoursunny think about that.
I might end up on one of those lists somewhere.
Sure, it would be better to add CF.
I never click ipv6 on virmach.
How about NY host @VirMach . My host has been down for week.
I'm not going anywhere near CF. Besides it is a three IPv4 VM so I also use it as a DNS server and an inbound only mail server. Similar issue with the IPv6 DNS and there is no IPv6 on the mail server because HE blocks port 25.
You are already on many lists and I keep adding you daily mwahahahahaha!
The Yeti has left the building.
Ha, nobody will recognize me now.
@mwahahahahaha! 🌹
TYOC030 and TYOC007 are offline?
Seems to be back to normal.
offline again :'(
I can't speak to TYOC030, but my VM on TYOC007 is doing fine.
EDIT: 20 minutes later my VMs on both TYOC039 and TYOC007 are unavailable.
Looks like a network issue in Tokyo, as all Tokyo nodes show as not reporting for the last 22 minutes on the status page.
TYOC039:
Operation Timed Out After 90001 Milliseconds With 0 Bytes Received
VirMach: Customer’s Service cannot use more than 10% of the monthly allocated bandwidth in under twenty-four (24) hours.
https://virmach.com/terms-conditions/#aup
TYOC025 offline?
Probably due to xTom changing ASN. Why didn't VirMach send any notification beforehand?
Looks like all nodes in Tokyo are back up. I'm showing that there was 1 hour and 2 minutes of downtime in Tokyo.
Operation Timed Out After 90001 Milliseconds With 0 Bytes Received @Tokyo again :'(
My fault on this one, not theirs. It was on my list but missed due to a few other things getting moved up in front of it.
Oof, that's a painful one to read. I haven't received any messages about my dedicated server going away, and just got (and paid for) the invoice for another year on mine. I guess that's what I get for not reading the forum very often
So, is that confirmation that my dedi is disappearing soon too, and if so, what can be done to get a refund on that invoice? I definitely don't need a couple hundred dollars of VPS credits.
LAXA018.VIRM.AC
Server monitoring, checking every 60 seconds. Has been down for unknown.
I checked statusbot.virm.ac @VirMach LAX2Z019 online
but my VPS is offline, can't be used, and the description :
Operation Timed Out After 90001 Milliseconds With 0 Bytes Received
been offline for a few days
There has been no updates on this one, I'm not sure what is going on with LAX2Z019 these days.
Just noticed this sale now!
https://virmach.com/special-offers/
The Ultimate Speedtest Script | Get Instant Alerts on new LES/LET deals | Cheap VPS Deals | VirMach Flash Sales Notifier
FREE KVM VPS - FreeVPS.org | FREE LXC VPS - MicroLXC
@Virmach do your servers at Dedipath offer the same 10 tbit ddos protection that Dedipath advertises for the dedis they sell and their vps?
New here, inquire about virmach's refugee plan
I've bought a virmach Tokyo's refugee server 2months ago.
It works perfectly in the first month, but when the time comes in August. it has been down for almost a month (Node has been locked ‘temporarily’)
I've opened a ticket, the operator seems noted the problem but not going to slove it. and then closed.
Does anyone know how long time will virmach took to repair the server or it just works for the first month?
Thank you
@virmach, I expect that @Artemis may be on TYOC029 which has not shown an update on the status page for a while.
i think Virmach is busy with the master server issue at the moment
I bench YABS 24/7/365 unless it's a leap year.
Really..... anyone knows how much issues per day they will meet? hahaha
too many.
I bench YABS 24/7/365 unless it's a leap year.
I think if they really wanna to slove the problem, it just take minutes
the comment for this refugee plan is "An rotational working"
Eg Tyoc 007 works for jan, feb mar
tyoc 0029 works for apr may jun.....
Maybe virmach can make a rotational monthly plan instead of a refugee ones
Does anyone knows if virmach count inbound transfer as bandwidth usage?
Yes
Both of these nodes are 99.9% uptime over last 6 months and the issues you're describing would only have affected a small fraction of customers, mostly related to spamming re-install requests as it was facing problems. TYOC029 was more complicated, definitely not "minutes" to resolve. I don't know what you believe we're doing this entire time.
We've been getting lots of tickets about it as it usually goes for Tokyo and this was done purposefully in this case. We just have to treat that location differently, as every update would bring in a bunch of tickets asking follow-up questions and it was a complicated matter that we were trying to avoid doing forced migrations to Los Angeles for as a quicker solution. We essentially had to go through every VM affected one by one multiple times and maybe spend an hour on each of them and then in the end most of them needed to get loaded back in carefully from disaster recovery backups, and a ton of other issues I don't want to get into but essentially 80-85% of people were online this entire time so it's not as large of an issue as something like LAX2Z019.
We could've left controls unlocked during the time if it wasn't a guaranteed crash every 6 hours from button mashing.
The New York node 027 has been down for a few months without any activity. Is it possible to migrate it to another location? I suspect that the New York node 027 might be completely unresponsive and beyond recovery.
Apologize for my word and thank you for your hard working..
As my experience , the VM works perfectly just in the first month.
And my friend's other virmach machine mostly work 99% like you say.
But mine has been down for about 1 month.
I understand it is a refugee plan, and you are not the UN High Commissioner for Refugees
Just hope it can online quickly.
Thank you
@VirMach
I didn't login to the billing portal for a long time,
Then recently when I tried to use the ticketing system, I feel that maybe your side get a lot of stress from some abusers through ticketing system, so I don't want to disturb you there.
If you have time, may I ask could you please help to make IPv6 working on Tokyo node?
There is no IPv6 for Tokyo, there is no IPv6 support at all. It was there in semi-deploy state, now it's totally not supported, don't ask, dont expect it to work.
https://billing.virmach.com/index.php?rp=/knowledgebase/67/IPv6.html#:~:text=We do not officially offer,one, troubleshooting one, etc.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
I think maybe they started to lose patience and feel angry (I can feel that through the page design of ticketing system
) for the abusers (and as this kinds of situation passing, even normal users) buying Tokyo node while getting more and more stress from ticketing system, so they lose the motivation for improving product there.
What I can recommend is why not make the price a little bit higher and kick all the stupid abusers away to have a fresh and nice daily mood.
Oh just realise the same issue... I have a VPS on LAX2Z019 also down now
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
I've gone through and overhauled our code for a lot of the stuff we've mentioned in the past to refine it and make sure it all works better in edge cases. The updates being pushed out over the weekend. This should mean the controls correctly break if an issue is detected related to a disk overloading, everything generally performing more uniformly, and more scenarios accounted for automatically when it comes to these issues. It's still not the version 2.0 we wanted to do on it all but it's an improvement.
Hivelocity has decided to vaguely and without notice disable ports on Chicago2 and Tampa, which we contacted them about today shortly after they were disabled. They said it might be a billing issue, turned on ports, sent it to billing department, and the billing department brought down the ports again and also brought it down for LAX2, citing abuse issues.
They're completely incapable of properly using their own systems, instead for some reason deciding to open tickets on multiple systems, then not correctly marking it as resolved on all systems. More recently it looks like they decided to use their LEGACY ticket system, which sends us 0 emails, and is hidden away, to open copies of old abuse reports that were already handled, plus a few new ones. They sent us an email directly about some of these, which I responded to multiple weeks ago and they ignored. This is where I explained these issues to them of them sending it over and over and it already being resolved for the ones they contacted us about at the time. Keep in mind none of these threats were active and most were handled already such a long time ago that no service even existed, others were already in a suspended state. In any case these were only about a 12 reported cases of abuse over a period of three months (out of multiple thousand IPv4 addresses.) They could've nullrouted the IP addresses as they always mention they'll do or which they do before they even send us the report in the past, yet someone in this company had to go through all this and decide it was a good decision to disable ports with no notice, to the point where even internally the network engineer assisting us had no idea what was going on and for some reason the billing department had to step in to figure out what was going on, only to disable ports again and then ignore our response so far.
Anyway, just making this comment so you guys realize how insane the situation is in case you're wondering what happened today. Let's see how they proceed after I went down and let them know of this again. I don't want you thinking this was our doing.
For reference, the only way for us to have been able to see these reports would have been to click this button, which is supposed to be old tickets from several months ago only. No email because the legacy system is not used for communication.
It's time to cancel Hivelocity and move everything to xTom.
We accept Karma donations for the last flan. 🍮 affbrr
They're also refusing to allow us to come pick up our equipment it seems until it's been reviewed by someone else. I don't even want to pretend to understand in what way that's related to the abuse issue described above, assuming any of it was even valid, like there's going to be phantom abuse that occurs after we pick up our equipment and have it hosted elsewhere? What's their end goal? To leave absolutely no level of trust left?
It's so sad that all the talented individuals that work there are essentially turned into paperweights until the people that caused the problems come back in the next day to remove the excessive red tape. And of course once they do show up, we already know they will be incapable of showing any remorse or taking any responsibility, they're only experts at getting defensive and shifting blame.
Chicago is down. Anyone else losing millions?
Cloudcone | Crunchbits | Dartnode | Dedirock | Georgedatacenter | Gigahost | Hostbilby | Host-c | Hostdzire | Hostsailor | Namecrane | Nuyek | Realtoxmedia | Servarica | Terabit | Tnahosting | Virmach