New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More
This discussion has been closed.

Comments
If you want a IP which currently isn't blocked you have to pay them like $5 I think and they don't guarantee that it'll stay unblocked
Thank you. That was actually a good read.
If it's like this, I think I'll just idle and cancel it afterwards.
TYOC039 Line Severe Packet Loss Ping Delay 1000 ms +
It's been two days. When will it recover?
same problem on TYOC039
it has been many times...
TYOC039 network down
Just copy-pasting e-mail if someone not checking e-mails on Sunday, but checks LET
I knew the bad situation about the migration.
But I still hope Virmach will solve these problems as soon as possible. I just made some suggestions and didn't create trouble.
Hi @VirMach my VM has been assigned with 4x ipv4 after I click Ryzen Migrate to Frankurt. Can you fix it or should I keep it. 😁

There was Ryzen Migrate button available for all three services. I did one migration successfully, but now the Ryzen Migrate option is gone and has been replaced by 'Migrate' with No data and With Data options costing $3 and $5 respectively. Anybody else experiencing the same?
Yes, free migrate is one time only (for now), so people stop moving VPS every 10 minutes to different nodes/locations. Maybe it will change in future, maybe not.
He's talking about servers that haven't yet migrated, my remaining virmach VPSes which haven't been migrated no longer show the option.
Then I would assume Ryzen migrate is disabled for now (Frankfurt died, LA died, NL gets rebooted today, Tokyo almost dead
) - probably shit ton of people clicking migrate on broken machines and making it even more broken + breaking other 
Nothing was official, pretty sure VirMach would say something if that was planned in longer terms :-)
TYOC002S is gone
And It's back!
@VirMach I'm not sure if you are aware, but ATLZ007 seems to be offline.
Billing looks fine (not doing "operation timed out"), SolusVM showed "An error occurred processing your request. The host is currently unavailable. Please try again later".
Not sure how long it has been off, but it's off at this moment.
TYOC039, “ping” more than 3 circles around the earth, very good!!!!
root@VIR-JP:~# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=56 time=1016 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=56 time=1343 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=56 time=1396 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=56 time=1495 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=56 time=1615 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=56 time=1309 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=56 time=1073 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=56 time=1422 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=56 time=1267 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=56 time=1378 ms
64 bytes from 1.1.1.1: icmp_seq=11 ttl=56 time=1439 ms
64 bytes from 1.1.1.1: icmp_seq=12 ttl=56 time=1107 ms
64 bytes from 1.1.1.1: icmp_seq=13 ttl=56 time=918 ms
64 bytes from 1.1.1.1: icmp_seq=14 ttl=56 time=670 ms
64 bytes from 1.1.1.1: icmp_seq=15 ttl=56 time=506 ms
64 bytes from 1.1.1.1: icmp_seq=16 ttl=56 time=1017 ms
64 bytes from 1.1.1.1: icmp_seq=17 ttl=56 time=750 ms
64 bytes from 1.1.1.1: icmp_seq=18 ttl=56 time=685 ms
64 bytes from 1.1.1.1: icmp_seq=19 ttl=56 time=1066 ms
64 bytes from 1.1.1.1: icmp_seq=20 ttl=56 time=1155 ms
64 bytes from 1.1.1.1: icmp_seq=21 ttl=56 time=1318 ms
64 bytes from 1.1.1.1: icmp_seq=22 ttl=56 time=1286 ms
64 bytes from 1.1.1.1: icmp_seq=23 ttl=56 time=1171 ms
64 bytes from 1.1.1.1: icmp_seq=24 ttl=56 time=1158 ms
64 bytes from 1.1.1.1: icmp_seq=25 ttl=56 time=1199 ms
64 bytes from 1.1.1.1: icmp_seq=26 ttl=56 time=891 ms
64 bytes from 1.1.1.1: icmp_seq=27 ttl=56 time=676 ms
64 bytes from 1.1.1.1: icmp_seq=28 ttl=56 time=546 ms
64 bytes from 1.1.1.1: icmp_seq=29 ttl=56 time=669 ms
64 bytes from 1.1.1.1: icmp_seq=30 ttl=56 time=619 ms
^C
Billing panel shows it offline, but it is not. I can ssh in just fine and it shows that it has not been rebooted for the past 24+ days.
@baolai TYOC039 ping seems better for the moment
But the transfer speed does not look too good. looks better as well
1 Mbs 3 Mbs 246 Kbs 1 Mbs
TYOC039 repaired (or abuser decided to stop)
Emm that's weird. Mine doesn't respond via SSH. Let me check when I get back to my desk. (maybe it was abuse?)
Just saying it is green across the board for me, so I don't know.
What do you use to keep track of that?
Nope. Mine isn't responding via SSH or HTTP... Definitely off for me it seems.
@xpreboun - I just went down as well. I now suspect that VirMach is doing some type of maintenance on the node and was shutting down VMs in an orderly fashion.
I just write my own stuff.
Dunno... I'm in a Whatever mode now
I've been idling the machines since all were provisioned (due to no IPv6)...
RYZE.ATL-Z007.VMS
Status Unknown
"An error occurred processing your request. The host is currently unavailable. Please try again later"
For anyone on AMS nodes:
Affecting System - AMSKVM9, AMSKVM8, AMSKVM7, AMSKVM6, AMSKVM5, AMSKVM4, AMSKVM3
06/26/2022 21:32 Last Updated 06/26/2022 21:37
Dear VirMach Customers,
Server migrations for Amsterdam to Frankfurt are currently in progress. We are starting with network re-configurations for your new IP addresses.
Thanks,
VirMach Support
See this > https://lowendtalk.com/discussion/comment/3444385/#Comment_3444385
I am confused why people from Amsterdam are getting migrated to Frankfurt rather than Amsterdam (?). I guess no capacity in new AMS?
Yeah, seems like it. Frankfurt would be the next nearest location.