All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
VirMach outage/migration status update
July 2, 2024:
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.
=====
July 1, 2024:
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.
Comments
Almost a year since my VPS is down. No way to get hold of that guy. Has cult following if you complain.
Priority ticket unanswered for over 3 months
The cult, thankfully, has been migrated to OGF.
lol the virmache migration saga never ends
This is a life style
Bought virmach - getting virmached. Expected.
Bought virmache, got heartache, might as well shitpost
We are being kicked out of Miami beach club.
Server wasn't prompting, so logged into the panel. They changed my ip address, and never sent out an email telling me.
LOL!!
My server was Atlanta.
nice company!
Before or after you updated the signature?
We are re-admitted into Miami beach club, but in the next tent.
MIAZ011 => MIAZ012
i love my roller coaster ride, every year must seek thrill.
One of my VirMache servers is named 'Hobo Harry' because it goes missing for a while, then shows up drunk in a new city.
Who?
Well, this is exhausting. Had a week or so of uptime but today my VPS in NYCB048 keeps going down.
We nevertheless have decided to exit the beach club.
It costs $3 to do a transfer, yet I could get a bigger VPS for $6/year, from a provider that has actual IPv6.
Transfer ticket has been pending for five days and counting.
MIAZ012 is broken.
We cannot load the controls for your service at this time.
This could either mean:
A) It took too long to load.
B) 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.
even @c1vhosting has better uptime