My shared hosting just auto-renewed. I'm tempted to see if PayPal can reverse it while the funds are still in transit. It's not something I would mind paying if there was any proof VirMach was still among the living. But as it stands, (at least my tickets) go unanswered for weeks... Just not a good sign. Could also be he got busted trying to smuggle his servers into or out of the datacenter. ¯\_(ツ)_/¯
@ATInDaHause said:
My VM at TPAZ005 is down and I couldn't access the Service Control, anyone else?
Erros message:
"We cannot load the controls for your service at this time.
This could either mean:
A) It took too long to load. The server controls have been automatically disabled due to an anomoly.
C) The server could be offline, in which case we have already been notified"
I'm still can't access the Service Control at TPAZ005 and the server isn't pinging, somebody else?
Edit, I think I spoke too soon. The httpd is able to serve content, but cPanel and the webmail interfaces remain inaccessible and return HTTP 500 errors.
Arrgh; migration and IP changes (again). Hope the one with multi-IP works out!
CHIZ001
CHIZ002
MIAZ011
MIAZ012
Most services in Miami will be migrated to Atlanta, and services in Chicago will be migrated to NYC Metro area.
In stasis until the shitposting stops/abates.
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).
Got this email from Virmach today, so someone is still alive.
Subject: Your LAX service is being migrated on July 2nd
Dear VirMach Customers,
We have extended the next due date of your service by +2 weeks to make up for any unexpected downtime faced with the short notice provided below.
On July 2nd, your service will be migrated from the Hivelocity downtown LAX datacenter to the QuadraNet Century LAX datacenter. The migration will start in the morning and conclude by the evening, barring any potential unexpected issues. Your IPv4 address will remain the same, but there may be some intermittent connectivity issues, expected to be faced for up to 48 hours after the migration.
Please check the network status page for any updates.
@Panda_233 said:
SJCZ007 The network is still not restored, VirMach what are you doing
The fix networking button didn't work for my VPS in SJC, I had to manually fix it in /etc/network/interfaces from the HTML5 VNC client. Basically changed "eth0" to "enp0s3" and then bring up the interface.
@Panda_233 said:
SJCZ007 The network is still not restored, VirMach what are you doing
The fix networking button didn't work for my VPS in SJC, I had to manually fix it in /etc/network/interfaces from the HTML5 VNC client. Basically changed "eth0" to "enp0s3" and then bring up the interface.
Panel for my SJC server still isn't loading zzz
Has been down for about 3 weeks according to hetrix.
@abjr said:
VM is running fine, but can't make changes due to the following message that I've received for months:
We have temporarily paused controls for this service as we are performing maintenance on the server. Please check back later.
This usually means we are aware of a problem and working to resolve it, or have purposefully temporarily removed controls to prevent potential issues with your service while we work on it. Your service may still be online and functioning normally, but if it is not, then check the network status page for any updates."
Finally opened a ticket (#467020) 10 days ago regarding this. No response. Is this provider just on auto-pilot now? A real shame as I've been a customer for years with no real problems.
Ticket not replied to, but this is actually working now. ¯ _(ツ)_/¯
Didn't realize my VPS on NYCB048 was also affected. I saw this on the Network Status page, looks like a larger migration:
LAX2 to LAX Migrations (Reported)Critical
Affecting System - LAX2Z018, LAX2Z020, LAX2Z021, NYCB042, NYCB048, NYCB006R
06/30/2024 00:05 - 07/03/2024 00:00 Last Updated 07/01/2024 02:01
There has been a delay in migration of approximately 60 individual virtual servers on LAX2Z020 and LAX2Z021. Originally planned for June 29th, these migrations will occur on June 30th. Services scheduled for migration on LAX2Z018 have also been delayed. ETA will be posted here when available.
All services have been credited 2 weeks instead of the original 1 week due to delayed notifications.
The following servers will be physically migrated on July 2nd:
NYCB006R
NYCB042
NYCB048
LAX2Z020
LAX2Z021
Anyone physically migrated will keep their original IPv4 address and remain on the same server. There may be an extended period of downtime should there be any issues or delays related to migration of IPv4 addresses or physical installation of servers. There is a small possibility that IPv4 addresses may be changed to reduce downtime should there be any unexpected delays or issues with networking.
Update: LAX2Z018 will be physically migrated on July 2nd instead of the original planned data transfer. We've made this decision as it would be a better experience to remain on the existing physical server, with a higher access to bursting resources.
(and this from yesterday):
VPShared -- LAX2Z017 (Outage)Critical
Affecting System - VPShared
07/01/2024 02:01 Last Updated 07/01/2024 02:06
Several attempts to stabilize the server have failed in the previous weeks, with the node continuing to face many novel issues consecutively. While it is online, these issues have essentially rendered your shared hosting service unusable.
We will begin performing further physical troubleshooting on July 2nd after the server is moved to a new datacenter location, and will likely need to perform emergency data recovery and migration to a stable node. We are determining the appropriate level of service extension given the scenarios faced on this server over an extended period of time, but you will likely receive several months of extension to make up for these previous issues.
My main NYC VPS is now inaccessible - node unknown; 185.221.22.0 subnet.
[Edit; All NYC down for me!]
In stasis until the shitposting stops/abates.
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).
Thu, 04 Jul 2024 08:47:00 -0700 We're investigating an outage in NYC. This appears to be a connectivity issue related to routing. We are communicating with the datacenter to resolve the issue.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
Had to rent a server from another provider, due to NYC fiasco. :'(
In stasis until the shitposting stops/abates.
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).
As said to client just 5 mins ago: Sod's Law back up just as I changed the DNS to the newly built replacement server. As I predicted.
In stasis until the shitposting stops/abates.
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).
@AlwaysSkint said:
As said to client just 5 mins ago: Sod's Law back up just as I changed the DNS to the newly built replacement server. As I predicted.
so did you go back to it and cancel your replacement server?
@JoeMerit said: so did you go back to it and cancel your replacement server?
I did revert to the NYC one but given upcoming CHI and MIA shenanigans, the newly built server may prove useful. It's significantly annoying due to me virtually idling the NYC server since BF 2019, to confirm its stability, which WAS solid as a rock.
In stasis until the shitposting stops/abates.
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).
@JoeMerit said: so did you go back to it and cancel your replacement server?
I did revert to the NYC one but given upcoming CHI and MIA shenanigans, the newly built server may prove useful. It's significantly annoying due to me virtually idling the NYC server since BF 2019, to confirm its stability, which WAS solid as a rock.
The NYC issue wasn't that complicated, but unfortunately it took very long to resolve just because of timing.
The amazing tech that usually helps with NYC was unavailable on the 4th so we were at the mercy of whoever happened to be on duty at the datacenter and as a result... let's just say if I was there, our usual tech was there, anyone from the direct partner we're using for NYC was there, or even if I was on a phone call with pretty much any of my non-technical friends or family members at the DC, it would have confidently been resolved in a couple hours.
@VirMach said: The NYC issue wasn't that complicated.. etc.
I hope that this is some form of reassurance. This specific NYC (multi-IP) has been excellent up to this point.
Awaiting the Sh1t to do the bad thing, when my BF'19 in CHI gets its IP change : pre-warned a client on that one. Still not clear on whether my MIA one will suffer be affected, during this bout of migrations.
In stasis until the shitposting stops/abates.
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).
In stasis until the shitposting stops/abates.
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).
193.29.97.0/24 is losing visibility.
MIAZ001 moving to Atlanta was scheduled for July 06 but I don't see new IP in SolusVM.
I'm glad that I didn't trust the "3-hoir downtime" and moved out most of the services on July 05.
We accept Karma donations for the last flan. 🍮 affbrr
Just you wait.. actually the migration is for CHIZ001 and CHIZ002 - guess where my VPS are?
In stasis until the shitposting stops/abates.
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).
@VirMach > Approximately 2 to 3 hours of downtime while your service is migrated.
You having a laugh? !
Looks as though I'm going to need to restore to that new competitor's server. What a bloody PITA. :-(
In stasis until the shitposting stops/abates.
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).
@yoursunny said:
193.29.97.0/24 is losing visibility.
MIAZ001 moving to Atlanta was scheduled for July 06 but I don't see new IP in SolusVM.
I'm glad that I didn't trust the "3-hoir downtime" and moved out most of the services on July 05.
New IP appeared in 89.37.197.0/24, MIAZ012.
Nevertheless, I plan to cancel this server.
$8.88/year 1920MB 45GB used to be good dealz but the Texas Josh has surpassed it.
We accept Karma donations for the last flan. 🍮 affbrr
I planned ahead a bit: verified VNC worked, switch from static to DHCP network config, and set a remote (UDP) syslog server.
My secondary VPS went down at 2024-07-07 09:13:41 (UTC+00:00) and moved from Miami to RYZE.ATL-Z010.VMS. Had to manually boot it, but it's now up and running again. I think that VPS has been in AMS, then FF, then Miami, and now ATL!
My 2GB free lifetime VPS (which has been really solid, thanks, Virmach!) on CHIZ001 went down at 2024-07-07 01:46:44 (UTC+00:00). Hetrixtools shows it flapped on/offline at least 16 times from 01:46 until 03:56. It's partially offline now--my remote syslog server is still seeing log entries over UDP, but it's clearly sad: "error resolving pool 0.debian.pool.ntp.org: Temporary failure in name resolution (-3)", so I suspect the network is passing traffic out, but not in.
I received the email a week ago indicating my VM was moving DCs due to IPv4 price hikes at the current provider. For some reason the email went to spam though I have since flagged it as not spam. As usual the downtime seems to have been grossly underestimated at 2-3 hours (needless to say this window came and went without any updates). Par for the course.
Logging in today I am getting the classic "We cannot load the controls for your service at this time." Since my service tickets never get responded to, anyone else in the 193.151.x.x range have their VMs moved yet and want to hazard a guess on when I should try to access mine again? I'll need to update DNS but I've never received advanced notice of the new target range IPv4 like pretty much all the rest of my providers give so just moving onto other things until it comes back online. Network status page seems to show all DCs up and online and I don't see any other maintenance notices or updates there so thought I would post here since it seems to be the only way I've ever received maintenance related info.
Logging in today I am getting the classic "We cannot load the controls for your service at this time." Since my service tickets never get responded to, anyone else in the 193.151.x.x range have their VMs moved yet and want to hazard a guess on when I should try to access mine again? I'll need to update DNS but I've never received advanced notice of the new target range IPv4 like pretty much all
My chi VPS was also in 193.151.183.0/24--no control panel access for me yet. Last I checked, the status page shows CHIZ001.VIRM.AC and CHIZ002.VIRM.AC have been offline for about 20 hours. Sorry, I know that's not much help.
Status page is now showing CHIZ001 and CHIZ002 are back online and my control panel is back--but with the old IP! I booted the VM and can access the console over VNC. It's got a DHCP lease, but I can't ping the gateway or the DHCP server. tcpdump shows 80+ other guests making DHCP queries (and some SSDP traffic, of course). Maybe something went wrong or took too long at NYC and CHI got a stay of execution? My syslog server hasn't seen anything from CHI since 22:03 UTC.
Logging in today I am getting the classic "We cannot load the controls for your service at this time." Since my service tickets never get responded to, anyone else in the 193.151.x.x range have their VMs moved yet and want to hazard a guess on when I should try to access mine again? I'll need to update DNS but I've never received advanced notice of the new target range IPv4 like pretty much all
My chi VPS was also in 193.151.183.0/24--no control panel access for me yet. Last I checked, the status page shows CHIZ001.VIRM.AC and CHIZ002.VIRM.AC have been offline for about 20 hours. Sorry, I know that's not much help.
All good, thanks. The fact that at least one other in my range is in the same state is a good enough update as any. At least I know my situation isn't unique to my VM. I'll keep checking back periodically.
@JBB said:
Status page is now showing CHIZ001 and CHIZ002 are back online and my control panel is back--but with the old IP! I booted the VM and can access the console over VNC. It's got a DHCP lease, but I can't ping the gateway or the DHCP server. tcpdump shows 80+ other guests making DHCP queries (and some SSDP traffic, of course). Maybe something went wrong or took too long at NYC and CHI got a stay of execution? My syslog server hasn't seen anything from CHI since 22:03 UTC.
Checked mine and seeing the same. Looks like something was either reverted or still in the process of moving/reassignment. VNC works same as you but old IP shows up and there's no other connectivity. Will check back on it again later.
Comments
My shared hosting just auto-renewed. I'm tempted to see if PayPal can reverse it while the funds are still in transit. It's not something I would mind paying if there was any proof VirMach was still among the living. But as it stands, (at least my tickets) go unanswered for weeks... Just not a good sign. Could also be he got busted trying to smuggle his servers into or out of the datacenter. ¯\_(ツ)_/¯
I'm still can't access the Service Control at TPAZ005 and the server isn't pinging, somebody else?
Shared hosting just came back online. Weird.
Edit, I think I spoke too soon. The httpd is able to serve content, but cPanel and the webmail interfaces remain inaccessible and return HTTP 500 errors.
SJCZ007 The network is still not restored, VirMach what are you doing
Smoking gange
The Yeti has left the building.
Arrgh; migration and IP changes (again). Hope the one with multi-IP works out!
In stasis until the shitposting stops/abates.
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).
Got this email from Virmach today, so someone is still alive.
Subject: Your LAX service is being migrated on July 2nd
Dear VirMach Customers,
We have extended the next due date of your service by +2 weeks to make up for any unexpected downtime faced with the short notice provided below.
On July 2nd, your service will be migrated from the Hivelocity downtown LAX datacenter to the QuadraNet Century LAX datacenter. The migration will start in the morning and conclude by the evening, barring any potential unexpected issues. Your IPv4 address will remain the same, but there may be some intermittent connectivity issues, expected to be faced for up to 48 hours after the migration.
Please check the network status page for any updates.
The fix networking button didn't work for my VPS in SJC, I had to manually fix it in /etc/network/interfaces from the HTML5 VNC client. Basically changed "eth0" to "enp0s3" and then bring up the interface.
Panel for my SJC server still isn't loading zzz
Has been down for about 3 weeks according to hetrix.
Ticket not replied to, but this is actually working now. ¯ _(ツ)_/¯
Didn't realize my VPS on NYCB048 was also affected. I saw this on the Network Status page, looks like a larger migration:
LAX2 to LAX Migrations (Reported)Critical
Affecting System - LAX2Z018, LAX2Z020, LAX2Z021, NYCB042, NYCB048, NYCB006R
06/30/2024 00:05 - 07/03/2024 00:00 Last Updated 07/01/2024 02:01
There has been a delay in migration of approximately 60 individual virtual servers on LAX2Z020 and LAX2Z021. Originally planned for June 29th, these migrations will occur on June 30th. Services scheduled for migration on LAX2Z018 have also been delayed. ETA will be posted here when available.
All services have been credited 2 weeks instead of the original 1 week due to delayed notifications.
The following servers will be physically migrated on July 2nd:
NYCB006R
NYCB042
NYCB048
LAX2Z020
LAX2Z021
Anyone physically migrated will keep their original IPv4 address and remain on the same server. There may be an extended period of downtime should there be any issues or delays related to migration of IPv4 addresses or physical installation of servers. There is a small possibility that IPv4 addresses may be changed to reduce downtime should there be any unexpected delays or issues with networking.
Update: LAX2Z018 will be physically migrated on July 2nd instead of the original planned data transfer. We've made this decision as it would be a better experience to remain on the existing physical server, with a higher access to bursting resources.
(and this from yesterday):
VPShared -- LAX2Z017 (Outage)Critical
Affecting System - VPShared
07/01/2024 02:01 Last Updated 07/01/2024 02:06
Several attempts to stabilize the server have failed in the previous weeks, with the node continuing to face many novel issues consecutively. While it is online, these issues have essentially rendered your shared hosting service unusable.
We will begin performing further physical troubleshooting on July 2nd after the server is moved to a new datacenter location, and will likely need to perform emergency data recovery and migration to a stable node. We are determining the appropriate level of service extension given the scenarios faced on this server over an extended period of time, but you will likely receive several months of extension to make up for these previous issues.
We apologize for the bad experience.
My main NYC VPS is now inaccessible - node unknown; 185.221.22.0 subnet.
[Edit; All NYC down for me!]
In stasis until the shitposting stops/abates.
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).
You are in the endless void man!!!!
The Yeti has left the building.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
Thu, 04 Jul 2024 08:47:00 -0700 We're investigating an outage in NYC. This appears to be a connectivity issue related to routing. We are communicating with the datacenter to resolve the issue.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
DALZ005 in virmach had been offlined.
DALZ005 was retired around 8 months ago. You're likely on another node, and if it went down today the highest likelihood is it's in NYC.
Had to rent a server from another provider, due to NYC fiasco. :'(
In stasis until the shitposting stops/abates.
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).
Hello @VirMach i'm write you more times to PM but I'm write in same time here , you are interested to sell you company? Or a subvention ?
Regards
OOOuuuuuuu
i like you are dreaming big
now i worry about you .... calm down .... slow and easy.
If you take over Virmach,please take care of these frustrated customers
What? Virmach for sale? I'll take it. $7
I promise to destroy the company in a few days.
26+ hours and counting
Powerful AMD Ryzen VPS (aff)
So, we can migrate down servers to another DC ? xD
As said to client just 5 mins ago: Sod's Law back up just as I changed the DNS to the newly built replacement server.
As I predicted. 
In stasis until the shitposting stops/abates.
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).
Back for 1.5 hours already.
Damn 4th of July.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
You're in for a long counting spree!!
Yay! The interface is back up. Now I can cancel it.
so did you go back to it and cancel your replacement server?
I did revert to the NYC one but given upcoming CHI and MIA shenanigans, the newly built server may prove useful. It's significantly annoying due to me virtually idling the NYC server since BF 2019, to confirm its stability, which WAS solid as a rock.
In stasis until the shitposting stops/abates.
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).
The NYC issue wasn't that complicated, but unfortunately it took very long to resolve just because of timing.
The amazing tech that usually helps with NYC was unavailable on the 4th so we were at the mercy of whoever happened to be on duty at the datacenter and as a result... let's just say if I was there, our usual tech was there, anyone from the direct partner we're using for NYC was there, or even if I was on a phone call with pretty much any of my non-technical friends or family members at the DC, it would have confidently been resolved in a couple hours.
I hope that this is some form of reassurance.
This specific NYC (multi-IP) has been excellent up to this point.
Awaiting the Sh1t to do the bad thing, when my BF'19 in CHI gets its IP change : pre-warned a client on that one. Still not clear on whether my MIA one will suffer be affected, during this bout of migrations.
In stasis until the shitposting stops/abates.
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).
CHi has bitten the dust.
In stasis until the shitposting stops/abates.
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).
193.29.97.0/24 is losing visibility.
MIAZ001 moving to Atlanta was scheduled for July 06 but I don't see new IP in SolusVM.
I'm glad that I didn't trust the "3-hoir downtime" and moved out most of the services on July 05.
We accept Karma donations for the last flan. 🍮 affbrr
Japan is the last one standing strong
I bench YABS 24/7/365 unless it's a leap year.
CHI is still working for me.
Just you wait.. actually the migration is for CHIZ001 and CHIZ002 - guess where my VPS are?
In stasis until the shitposting stops/abates.
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).
Ah, that explains it. I'm not on those nodes. ...New Yoik?
@VirMach > Approximately 2 to 3 hours of downtime while your service is migrated.
You having a laugh? !
Looks as though I'm going to need to restore to that new competitor's server. What a bloody PITA. :-(
In stasis until the shitposting stops/abates.
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).
on the bright side, my long offline NY server is back up and I got credited for all the downtime and then some.
New IP appeared in 89.37.197.0/24, MIAZ012.
Nevertheless, I plan to cancel this server.
$8.88/year 1920MB 45GB used to be good dealz but the Texas Josh has surpassed it.
We accept Karma donations for the last flan. 🍮 affbrr
You'll want a push-ups video to transfer the server?
Have you tried turning it off and on again?I planned ahead a bit: verified VNC worked, switch from static to DHCP network config, and set a remote (UDP) syslog server.
My secondary VPS went down at 2024-07-07 09:13:41 (UTC+00:00) and moved from Miami to RYZE.ATL-Z010.VMS. Had to manually boot it, but it's now up and running again. I think that VPS has been in AMS, then FF, then Miami, and now ATL!
My 2GB free lifetime VPS (which has been really solid, thanks, Virmach!) on CHIZ001 went down at 2024-07-07 01:46:44 (UTC+00:00). Hetrixtools shows it flapped on/offline at least 16 times from 01:46 until 03:56. It's partially offline now--my remote syslog server is still seeing log entries over UDP, but it's clearly sad: "error resolving pool 0.debian.pool.ntp.org: Temporary failure in name resolution (-3)", so I suspect the network is passing traffic out, but not in.
Fingers crossed we don't have any major problems!
I received the email a week ago indicating my VM was moving DCs due to IPv4 price hikes at the current provider. For some reason the email went to spam though I have since flagged it as not spam. As usual the downtime seems to have been grossly underestimated at 2-3 hours (needless to say this window came and went without any updates). Par for the course.
Logging in today I am getting the classic "We cannot load the controls for your service at this time." Since my service tickets never get responded to, anyone else in the 193.151.x.x range have their VMs moved yet and want to hazard a guess on when I should try to access mine again? I'll need to update DNS but I've never received advanced notice of the new target range IPv4 like pretty much all the rest of my providers give so just moving onto other things until it comes back online. Network status page seems to show all DCs up and online and I don't see any other maintenance notices or updates there so thought I would post here since it seems to be the only way I've ever received maintenance related info.
Cheers.
My chi VPS was also in 193.151.183.0/24--no control panel access for me yet. Last I checked, the status page shows CHIZ001.VIRM.AC and CHIZ002.VIRM.AC have been offline for about 20 hours. Sorry, I know that's not much help.
Status page is now showing CHIZ001 and CHIZ002 are back online and my control panel is back--but with the old IP! I booted the VM and can access the console over VNC. It's got a DHCP lease, but I can't ping the gateway or the DHCP server. tcpdump shows 80+ other guests making DHCP queries (and some SSDP traffic, of course). Maybe something went wrong or took too long at NYC and CHI got a stay of execution? My syslog server hasn't seen anything from CHI since 22:03 UTC.
If you want it, $6.99 (PayPal) or $6.66 (Venmo), seller pays transaction fee and transfer service fee.
Server will be loaded with one push-up video.
YABS https://lowendspirit.com/discussion/comment/98747/#Comment_98747
We accept Karma donations for the last flan. 🍮 affbrr
All good, thanks. The fact that at least one other in my range is in the same state is a good enough update as any. At least I know my situation isn't unique to my VM. I'll keep checking back periodically.
Checked mine and seeing the same. Looks like something was either reverted or still in the process of moving/reassignment. VNC works same as you but old IP shows up and there's no other connectivity. Will check back on it again later.
I'll take it. How much is the transfer service fee?