Node ATLZ032 has been offline for almost three months, and was offline for nearly half a month before its expiration.
Actually, I could have just given up on renewing, but I chose to renew because I believe the company will fix it eventually.
(With the node online, I dare not submit support tickets for flash sale devices other than those for network failures.)
If it is confirmed that the node (ATLZ032) does not exist, could you consider migrating it to any available node to bring it online (e.g., Los Angeles)? Alternatively, could you provide feedback on when the Atlanta node is expected to return to online status? Thank you.
I have a VPS that for 2 months has not been able to boot. 2 months with a ticket in and AI response but unfixed. Pleasantries are now being put aside. If they can't fix it in the next couple of days, I'm done with this company.
RCLOUDSYSTEMS - EmailBackup and EmailSync are powerful email management and migration utilities for an unbeatable price!
Congratulations @jcn50 your campaign against VirMach has been successful as his provider tag has been removed. Not sure who did this as there has been no comment by the moderators.
Will you maybe give it a rest now?
@bmoto said:
Congratulations @jcn50 your campaign against VirMach has been successful as his provider tag has been removed. Not sure who did this as there has been no comment by the moderators.
Will you maybe give it a rest now?
@bmoto said:
Congratulations @jcn50 your campaign against VirMach has been successful as his provider tag has been removed. Not sure who did this as there has been no comment by the moderators.
Will you maybe give it a rest now?
TierHive - Hourly VPS - NAT Native - /24 per customer - Lab in the cloud - Free to try. | I am Anthony Smith FREE tokens when you sign up, try before you buy. | Join us on Reddit
@bmoto said:
Congratulations @jcn50 your campaign against VirMach has been successful as his provider tag has been removed. Not sure who did this as there has been no comment by the moderators.
Will you maybe give it a rest now?
Some updates on specific nodes that have been facing an extended outage.
ATLZ030 - Data loss on 7x VMs. Service extended by 160 days. Not yet back online, requires some more work.
ATLZ031 - In the process of being migrated/partially migrated. Extensions occur as migration is complete.
ATLZ032 - Queued for migration after ATLZ031. Service extended by 90 days.
LAXA017 - Back online after network issues. Service extended by 30 days.
AMSD018 - In addition to previously described data loss, it's unstable. Migrations started 2-3 weeks ago, and are ongoing. If your service was not affected by the data loss it will come back online after migration and service extended individually.
CHIZ035 - Small quantity of services are on this node. This was worked on but unable to stabilize. Unless a migration occurs sooner, the plan is to address it in an upcoming Chicago visit (unfortunately delayed, was meant to happen this week.)
AMSD025 - Went back down after being brought back online. Motherboard issue. Will be looked at again this week but the plan will be to stabilize it for migrations.
SJCZ001, SJCZ009, SJCZ010 -- These are in Los Angeles and waiting for an IP change.
All others will be migrated as previously discussed. I had a tire blowout on the drive back which added some time to the trip, and while I didn't lose control of the vehicle, the servers need to be individually checked since it was a rough ride/tow. Hopefully will be completed by the end of the week.
I may provide some additional details on what exactly happened to this location at a later time.
Los Angeles Update
Network should now be stable, pending a final check. For reference there were issues which were already fixed, but re-appeared during last week's maintenance. I made some improvements during the maintenance for long-term stability. If you are still facing issues, please let me know.
Some servers ran into brief issues during the maintenance and these issues were resolved (you may have lost connectivity, a couple servers needed to be rebooted and one server needed a disk swap.)
Seeing as the infantile imok thinks this is a cookery forum: out of the frying pan and into the fire.
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural. It wisnae me! A big boy done it and ran away. || NVMe2G for life! until death (the end is nigh).
Network should now be stable, pending a final check. For reference there were issues which were already fixed, but re-appeared during last week's maintenance. I made some improvements during the maintenance for long-term stability. If you are still facing issues, please let me know.
My Los Angeles VPS is located at node: LAXA009
Based on my test results from a few minutes ago, the network still experiences intermittent connectivity issues:
@bmoto said:
Congratulations @jcn50 your campaign against VirMach has been successful as his provider tag has been removed. Not sure who did this as there has been no comment by the moderators.
Will you maybe give it a rest now?
Comments
Node ATLZ032 has been offline for almost three months, and was offline for nearly half a month before its expiration.
Actually, I could have just given up on renewing, but I chose to renew because I believe the company will fix it eventually.
(With the node online, I dare not submit support tickets for flash sale devices other than those for network failures.)
If it is confirmed that the node (ATLZ032) does not exist, could you consider migrating it to any available node to bring it online (e.g., Los Angeles)? Alternatively, could you provide feedback on when the Atlanta node is expected to return to online status? Thank you.
(View Ticket #984345)
I renewed one last year and It has been offline since then. I am about to renew it again
Virmach Deals
I have a VPS that for 2 months has not been able to boot. 2 months with a ticket in and AI response but unfixed. Pleasantries are now being put aside. If they can't fix it in the next couple of days, I'm done with this company.
RCLOUDSYSTEMS - EmailBackup and EmailSync are powerful email management and migration utilities for an unbeatable price!
LOL
Hahaha..... the suckers' honeypot......
💩 VirCrap 💩
Good morning
No flan today. It's going to be Arroz con leche.
Congratulations @jcn50 your campaign against VirMach has been successful as his provider tag has been removed. Not sure who did this as there has been no comment by the moderators.
Will you maybe give it a rest now?
Maybe @AnthonySmith did it.
Anyway, the arroz con leche was delicious, I still have more for a couple of days. No flan this month. Too much sugar.
I don't think Virmach is going to dissappear... again... probably
Yep.
Like I said they don't advertise or respond here, literally makes no difference, happy for them to get in touch any time to discuss.
TierHive - Hourly VPS - NAT Native - /24 per customer - Lab in the cloud - Free to try. | I am Anthony Smith
FREE tokens when you sign up, try before you buy. | Join us on Reddit
~old~ new Sheriff in town.
Welcome back!
blog | exploring visually |
Some updates on specific nodes that have been facing an extended outage.
ATLZ030 - Data loss on 7x VMs. Service extended by 160 days. Not yet back online, requires some more work.
ATLZ031 - In the process of being migrated/partially migrated. Extensions occur as migration is complete.
ATLZ032 - Queued for migration after ATLZ031. Service extended by 90 days.
LAXA017 - Back online after network issues. Service extended by 30 days.
AMSD018 - In addition to previously described data loss, it's unstable. Migrations started 2-3 weeks ago, and are ongoing. If your service was not affected by the data loss it will come back online after migration and service extended individually.
CHIZ035 - Small quantity of services are on this node. This was worked on but unable to stabilize. Unless a migration occurs sooner, the plan is to address it in an upcoming Chicago visit (unfortunately delayed, was meant to happen this week.)
AMSD025 - Went back down after being brought back online. Motherboard issue. Will be looked at again this week but the plan will be to stabilize it for migrations.
No updates, listing for clarity:
San Jose Update
All others will be migrated as previously discussed. I had a tire blowout on the drive back which added some time to the trip, and while I didn't lose control of the vehicle, the servers need to be individually checked since it was a rough ride/tow. Hopefully will be completed by the end of the week.
I may provide some additional details on what exactly happened to this location at a later time.
Los Angeles Update
Network should now be stable, pending a final check. For reference there were issues which were already fixed, but re-appeared during last week's maintenance. I made some improvements during the maintenance for long-term stability. If you are still facing issues, please let me know.
Some servers ran into brief issues during the maintenance and these issues were resolved (you may have lost connectivity, a couple servers needed to be rebooted and one server needed a disk swap.)
Seeing as the infantile imok thinks this is a cookery forum: out of the frying pan and into the fire.
Than=compare;then=sequence:brought=bring;bought=buy:staffs=pile of sticks:informations/infos=no plural.
It wisnae me! A big boy done it and ran away. || NVMe2G for life! until death (the end is nigh).
My Los Angeles VPS is located at node: LAXA009
Based on my test results from a few minutes ago, the network still experiences intermittent connectivity issues:
@VirMach how many physical servers do you have running?
Everything runs on cloud by VirBot™
Nothing is physical
Neither @FrankZ nor @VirMach is real
So... Psychological servers?
Yes, a rest, please.
Schrödingermachfrei.
My pronouns are like/subscribe.
Everything is in your mind