AlphaVPS Outage History

Started Jul 30, 2026, 12:50 PM UTC· resolved Aug 21, 2026, 11:11 AM UTC

1. identified Jul 30, 2026, 12:50 PM UTC

   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.

2. identified Jul 30, 2026, 01:13 PM UTC

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

3. identified Jul 30, 2026, 01:25 PM UTC

   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.

4. identified Jul 30, 2026, 02:00 PM UTC

   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.

5. identified Jul 31, 2026, 10:55 AM UTC

   SOFSTORAGE06 maintenance is done and all VMs are booting up.

6. resolved Aug 21, 2026, 11:11 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 29, 2026, 06:42 PM UTC· resolved Jul 09, 2026, 03:44 AM UTC

1. identified Jun 29, 2026, 06:42 PM UTC

   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.

2. identified Jun 29, 2026, 07:39 PM UTC

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

3. identified Jun 29, 2026, 08:01 PM UTC

   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.

4. identified Jun 29, 2026, 09:22 PM UTC

   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.

5. monitoring Jun 30, 2026, 12:52 AM UTC

   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.

6. monitoring Jun 30, 2026, 07:30 AM UTC

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

7. monitoring Jun 30, 2026, 07:36 AM UTC

   We are continuing to monitor for any further issues.

8. monitoring Jun 30, 2026, 04:38 PM UTC

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

9. resolved Jul 09, 2026, 03:44 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 27, 2026, 12:56 PM UTC· resolved Jun 30, 2026, 12:51 AM UTC

1. identified May 27, 2026, 12:56 PM UTC

   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.

2. monitoring May 27, 2026, 03:28 PM UTC

   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.

3. resolved Jun 30, 2026, 12:51 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 07, 2026, 09:31 AM UTC· resolved Jun 30, 2026, 12:52 AM UTC

1. identified Apr 07, 2026, 09:31 AM UTC

   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.

2. resolved Jun 30, 2026, 12:52 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 22, 2025, 10:05 PM UTC· resolved Sep 26, 2025, 07:02 PM UTC

1. investigating Sep 22, 2025, 10:05 PM UTC

   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.

2. identified Sep 24, 2025, 05:35 PM UTC

   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.

3. resolved Jan 29, 2026, 08:02 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 04, 2025, 05:13 AM UTC· resolved Sep 04, 2025, 05:26 AM UTC

1. investigating Sep 04, 2025, 05:13 AM UTC

   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.

2. resolved Sep 04, 2025, 05:26 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 03, 2025, 05:09 AM UTC· resolved Sep 03, 2025, 07:33 AM UTC

1. identified Sep 03, 2025, 05:09 AM UTC

   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.

2. identified Sep 03, 2025, 05:27 AM UTC

   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.

3. resolved Sep 03, 2025, 07:33 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 04, 2025, 03:15 AM UTC· resolved Jul 09, 2025, 08:33 AM UTC

1. identified Jul 05, 2025, 08:58 AM UTC

   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

2. resolved Jul 09, 2025, 08:33 AM UTC

   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

Read the full incident report →

Started Jun 25, 2025, 04:40 PM UTC· resolved Jun 26, 2025, 07:44 AM UTC

1. identified Jun 25, 2025, 04:40 PM UTC

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

2. resolved Jun 26, 2025, 07:44 AM UTC

   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.

Read the full incident report →

Started May 31, 2025, 03:59 AM UTC· resolved May 31, 2025, 12:59 PM UTC

1. identified May 31, 2025, 03:59 AM UTC

   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.

2. resolved May 31, 2025, 12:59 PM UTC

   The incident is fully resolved.

Read the full incident report →

Started Dec 20, 2024, 07:49 AM UTC· resolved Jan 01, 2025, 12:08 PM UTC

1. investigating Dec 20, 2024, 07:49 AM UTC

   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.

2. identified Dec 20, 2024, 09:31 AM UTC

   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.

3. identified Dec 20, 2024, 01:54 PM UTC

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

4. identified Dec 20, 2024, 09:04 PM UTC

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

5. monitoring Dec 21, 2024, 02:01 PM UTC

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

6. monitoring Dec 21, 2024, 03:44 PM UTC

   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.

7. monitoring Dec 21, 2024, 11:35 PM UTC

   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.

8. resolved Jan 01, 2025, 12:08 PM UTC

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

Read the full incident report →