Alphavps outage history

We have begun preemptive hardware maintenance on the following nodes: SOFSTORAGE01 SOFSTORAGE06 SOFSTORAGE07 VPS instances hosted on the affected nodes may experience a temporary interruption. The expected downtime is approximately 15 to 30 minutes per VPS. Our team is monitoring the maintenance closely and will provide further updates as the work progresses.

We're beginning work on SOFSTORAGE07. VMs have been gracefully shutdown and will be booted back up shortly.

We have completed the work on SOFSTORAGE07 and virtual machines are booting back up. We're moving forward with SOFSTORAGE01, virtual machines are being shutdown and maintenance begins.

We have completed the work on SOFSTORAGE01 and virtual machines are booting back up. We're moving forward with SOFSTORAGE06, virtual machines are being shutdown and maintenance begins.

SOFSTORAGE06 maintenance is done and all VMs are booting up.

We are currently experiencing a large-scale DDoS attack targeting portions of our network infrastructure. This attack is causing intermittent connectivity issues and increased latency for some customers. Our network engineering team is actively working to deploy additional permanent mitigation measures to fully address this attack and further strengthen the resilience of our infrastructure. Temporary mitigation is already in place, and we continue to monitor and adapt our defenses as the attack evolves. We sincerely apologize for any disruption this may cause and appreciate your patience while we work toward a complete and permanent resolution. Further updates will be provided as progress is made.

We are continuing to work on a fix for this issue.

We've applied mitigation in Nuremberg. Sofia is pending and should be applied shortly. As we're dealing with an extortion/ransom DDoS attacks, we're unable to share more details publically.

While the malicious attackers are constantly changing the attack patterns, we're applying mitigation and the majority of our customers are back online. We're engaging local law enforcement in the situation as well. Further information to follow.

We've implemented mitigation across all of our locations and traffic has returned to normal. There might be variances in ICMP, but we trust that the issue is getting resolved in full.

We're continuing to monitor the situation and apply mitigation adjustments. All services across all locations are online and are considered stable currently.

We are continuing to monitor for any further issues.

We're monitoring the situation and tuning mitigation profile across locations to ensure seamless work of the mitigation appliances with minimal interruptions.

This incident has been resolved.

We have started urgent network maintenance in our New York location to deploy new upstream connectivity following the unexpected exit of our current provider from the facility. Further details are sent via email to all affected virtual machine clients. During this maintenance, some customers may experience intermittent connectivity interruptions or temporary downtime while network migration activities are performed. The maintenance window is expected to last up to 8 hours, although we believe the actual disruption will be significantly shorter. We sincerely apologize for the short notice and any inconvenience caused. This upgrade is an important step toward improving the long-term stability and quality of our New York services. Further updates will be posted here as progress continues.

We have finished with the network upgrade and as of 1 hour - all network is stable. We'll continue monitoring for a few more hours, until we close the case.

This incident has been resolved.

A critical RAID array failure occurred on dalstorage01 earlier today. The RAID controller entered an unstable state and continued write operations, which resulted in corruption of multiple KVM disk images. The node was taken offline immediately to prevent further impact. The RAID controller has been replaced and recovery procedures are currently in progress. Due to the array size, recovery is time-intensive and data consistency cannot be guaranteed. At this time, available capacity in Dallas is limited. We are actively working on deploying additional hardware, however an exact ETA is not yet confirmed. Affected customers are being provided with replacement services in alternative locations. Rescue access can be enabled upon request for best-effort data recovery. Further updates will be provided as progress continues. If your VPS is affected by this, you have already been sent an email with further steps. If no email is sent to you - please open a ticket immediately.

This incident has been resolved.

We've been alerted of an issue with our sofstorage22 node. We've dispatched DC engineers to check the status of the server and attempt recovery.

We continue working on the sofstorage22 host node. Unfortunately, at the moment we're unable to restore the RAID array. We're continuing with data recovery and further updates will be posted within 24 hours.

This incident has been resolved.

We've been alerted of a problem with our nuestorage03 KVM storage Node. Upon checking, we've discovered the node is completely unreachable by IPMI. We've dispatched on-site techs to check the condition of the node. Further updates to follow.

This incident has been resolved.

We've been alerted by our system that our nueryzenkvm01 host node is currently down. As we're unable to open an IPMI connection, we have engaged Datacenter technicians on-site. Updates to follow.

We're currently experiencing a hardware failure and we'll be replacing some parts of the chassis with on-site spares. ETA of resolution: 2-3 hours.

This incident has been resolved.

On July 4th, 2025, we detected a catastrophic RAID10 SSD array failure on node nueovz04. Fortunately, this node was in the process of being decommissioned and actively migrated to new infrastructure, so the impact is limited to a small number of customers. Since discovery, we have attempted multiple recovery approaches, including replacing RAID controllers and utilizing advanced data recovery techniques. We are currently preparing an identical server chassis to import the array and attempt further recovery efforts. At this time, we cannot guarantee recovery success or provide a precise ETA, but we are targeting the first half of the upcoming week for the next update or resolution. We sincerely apologize for the inconvenience and thank you for your patience while we work through this. — The AlphaVPS Team

Status: Recovery Unsuccessful – Services Being Recreated Following extensive recovery efforts on node nueovz04, we regret to inform you that we have not been able to restore the RAID10 SSD array. Our team has attempted: - Replacing the RAID controller cache - Replacing the entire RAID controller with multiple known working controllers - Transplanting the drives into an identically configured chassis, with fully matching firmware and hardware Despite all recovery attempts, the RAID array remains inaccessible. At this stage, we must consider the data on this node to be lost. We are now moving forward with recreating affected services on a new node. Our team will be reaching out individually to each impacted customer to coordinate this process. If you were hosted on nueovz04 and have not received an email from us, we urge you to contact our support team as soon as possible. We deeply regret this outcome and sincerely apologize for the disruption. Thank you for your patience and understanding during this time. — The AlphaVPS Team

We've detected an issue with our sofovz06 node. We're working on resolving it. Please stand by for updates.

We've resolved the issue as of 14 hours ago. We've monitored the situation throughout the time and believe that system is now stable.

We've been informed of an urgent DataCenter maintenance in our NYC facility, affecting some of our services there. ETA of service restoration is 1-2 hours.

The incident is fully resolved.

We've been alerted of a catastrophic RAID failure on our nuestorage07 node. Earlier this morning, the controller started flapping, which jumped the I/O load to over 90. This made every VM on the host hypervisor unresponsive. We've proceeded with replacing the RAID adapter and we're moving towards an attempted recovery. At this point, we're unsure if recovery would be possible.

We're currently working on bringing the node back online in a stable state. We estimate that it would take us 3-4 additional hours before we start booting the virtual machines up and assessing the damage. Please stand by for further updates.

We are starting with restoration of individual KVM machines. Further updates to follow.

We're continuing to work on restoring VMs, if your VM is affected - please wait until it's booted up.

We'll be booting up the remaining virtual servers in the next 1 hour and continue with monitoring the hypervisor.

Unfortunately, as we booted up the majority of the affected VMs, the node started becoming unstable again with flush operations starting to get queued. We're looking into alternative solutions at the moment. Further updates to come.

We've proceeded with replacing additional hardware. After we've performed manual fsck on each virtual machine's virtual drive - we've proceeded with booting up all affected VPS. As of now, all services are restored. We'll be monitoring the situation throughout the next days.

We've monitored the situation for the past 11 days and as of now, everything is stable and we're closing the issue.

We've identified an issue with our Nuremberg network. We're working on resolving it.

A fix has been implemented. The issue was related to a reboot of a virtual chassis member, causing multiple BGP sessions to start flapping. We're monitoring the environment and we'll apply further fixes as necesary.

We've been monitoring the situation and a fix has been implemented for this specific edge case. We're closing this as resolved.

Our monitoring has alerted us that our laxryzenkvm07 node is currently offline. During our investigation, we've found out that we're unable to reach IPMI/BMC as well. We're dispatching on-site technicians to check the status of the server. Further updates to follow!

Services are back online now.

Our engineers have identified an upstream-related problem, causing packet loss from certain routes towards our London infrastructure. The issue was identified to be upstream-caused. We're awaiting our London connectivity partners to further update us with an estimation of time for service restoration.

The issue seems to be currently resolved but we're awaiting updates from our upstream. We will keep monitoring throughout the day.

Our London connectivity partners state that the issue has been identified and resolved. We will continue to monitor the network throughout the day.

As per now - we consider this to be resolved.

We've identified a hardware issue with our nueovz04 node and we've immediately taken it offline, pending remote hands in DC to swap some hardware components.

The node is back online and we'll be monitoring it for stability and further issues.

This incident has been resolved.

Hello, We've identified an issue in our Sofia location, affecting our network. We've isolated it to our QFX Virtual Chassis Core. We've restored back connectivity on a single member of our Virtual Chassis and no redundancy is present at the moment. We're working on bringing the rest of our VC members online to restore redundancy.

We've identified the main problem, which was related to one of the members of our Juniper QFX Virtual Chassis. At the moment, we believe that one of the virtual chassis members suffered a catastrophic failure of internal storage. Unfortunately, this specific Juniper QFX device was the active master in our VC configuration. As per best practices, we run multiple devices, which can take over the mastership when the current master fails, however in this case - this has not happened, as JunOS was partially running on the failing device. The master killed the internal routing sessions and no packets were being transmitted via the secondary devices. Once we determined the root cause, we've done a manual switchover to another VC member and connectivity was restored. We're working on replacing the failing device and bringing it back in our VC to restore redundancy. Service redundancy should still be considered to be at risk. IPv6 connectivity is not restored on 100% yet, as our priority is bringing v4 redundancy back in place. Further updates to follow.

As of now, IPv6 connectivity is also restored. We're proceeding with replacing the virtual chassis member.

We've installed a new QFX member, after initial configuration and restored full redundancy. As of now, all systems are back to being fully redundant again. We'll continue monitoring the infrastructure and close this issue later today.

We're closing this incident as resolved.

As per our previous email - we're beginning the pre-scheduled migration of nuestorage* nodes.

We're taking down nuestorage01 node down.

Nuestorage01 is ready and booting up, nuestorage02 is currently being shutdown.

We've shutdown nuestorage03. As of the moment - nuestorage02 shows further hardware problems and we'll shut it down again to further debug.

We've completed the maintenance on nuestorage03 and we've taken back nuestorage02 for further checks. As of now - both nuestorage01 and nuestorage03 can be considered stable.

nuestorage02 node is back up and running. As of now - all nodes are back online and all instability issues should be permanently resolved! We're closing this as resolved.

Our monitoring has detected network connectivity issues and packetloss in our LAX location. This seems to be related to our upstream and is out of our scope. We're currently awaiting their network engineers to sort out the problem.

A fix has been implemented and we are monitoring the results.

The incident has been resolved and the main cause was a significant peering disturbance in the LA ANY2 peering platform.

We've started the pre-scheduled network maintenance in Sofia. Minor and short service disruptions might occur.

We've completed the maintenance without any disruption to client services and are closing the maintenance window.

We're investigating a complete network outage in London, related to our upstream. Further news to follow.

As of now, we've restored connectivity to the majority of our clients in London. A small portion of clients residing on a specific network segment are still affected. We're dealing with a large-scale network attack and working closely with our upstreams on completely mitigating the attack.

Our upstream applied some additional mitigation rules on the Corero device and as of now - all clients are back online.