jtk
jtk
Comments
-
I was about to report 3 VMs down, and awaiting a dedi re-install for about 10 days until I looked again, and another 2 VMs have since went unreachable. The network status page was updated today, so that's a good sign, but less helpful if you don't have a record of which node a VM you're on. Here's to hoping all will be…
-
Regretfully I just starting to do the opposite. I've cancelled what was a decent 2020 deal already. A few others I'm probably going to cancel that are now in extended outages. It probably is no big loss to VirMach and I hope things work out, but I can't justify rewarding a provider with renewals based on the hope things…
-
Perfect, thank you. If not already claimed, I'll lay stake to: * vps32 * vps67 * vps72 * vps76 * vps114 * vps115 * vps129 * vps144 * vps157 * vps166 * vps198 But I need to go figure out which ones, if any, allow transfers. OK to follow up in a direct message?
-
Any chance you could include what the first octet of the IPv4 address? I might be interested in some depending where in the address they are.
-
Cool, thanks. I used to have one there with you, but I think that was on an OpenVZ that eventually went EOL. If I order one, submit a ticket if it doesn't land in 205/8?
-
Seems gimmicky and unnecessary for you to try to live up to. Plus, for many low-end customer who's been around awhile, any lifetime VPS plan is going to conjure up only negative associations with one notorious at cost "provider" .
-
Looking for guidance on how to report/track outstanding problems that I think likely require some actual support from VirMach. I've had dozens of dozens migrated successfully, but I have at least the following outstanding problems: * A system (on RYZE.ATL-Z005.VMS) was successfully migrated, but is missing two additional…