Hypervisor Outage

Some VPS management features that were temporarily disabled due to high system load have now been re-enabled. These include:

* Boot / Reboot
* VNC access
* Root password reset
* rDNS management
* Debian OS

Please note that Boot / Reboot and Root password reset operations are processed via a queue. Allow some time for these actions to complete once initiated.

Approximately 60% of affected virtual machines have now been successfully restored. Further updates will be communicated to affected clients via email over the coming week.

Re-installation of services are made available for the clients. The re-install tasks could take 3-6 hours to complete as the system works on a queue.

Recovery of affected Los Angeles VPS nodes is in progress; customers will be able to reinstall and restore services once rebuilds are complete.

We are continuing recovery efforts following a security incident that impacted a limited portion of our Los Angeles VPS infrastructure.

The affected systems were promptly isolated, and our engineering teams are rebuilding impacted nodes from a clean state. Platform-level security reviews and additional safeguards are being applied as part of this process.

At this time:

* The incident has been contained
* Only a subset of VPS infrastructure was affected
* Core systems, billing platforms, and customer databases remain unaffected

Once rebuilding and validation are complete, affected customers will be able to reinstall their VPS and restore services. Detailed guidance and timelines will be communicated directly to impacted users via email.

We appreciate your patience while we complete the recovery and strengthen our platform. Further updates will be posted here as progress continues.

**What We First Observed**

We were initially alerted to the incident when our monitoring systems detected that several virtual machines experienced network connectivity issues. Upon investigation, we observed abnormal system behavior during the boot process on a subset of affected VMs.

Our engineering teams immediately isolated the impacted servers and began a detailed technical investigation. During this process, we identified signs of unauthorized system-level modification on affected virtual machines, and recovery efforts were initiated.

We are actively exploring all viable recovery options, including low-level disk analysis and filesystem validation, while preparing contingency plans to ensure services can be restored as quickly as possible.

**How the Incident Occurred**

As part of the investigation, our team identified that an unauthorized script had been executed on the affected nodes. Evidence suggests that this activity originated through management-layer access rather than direct SSH connectivity, which explains the absence of anomalous SSH login records.

During our review, we also identified irregularities in logs associated with a single VPS management instance responsible for coordinating the affected nodes. Based on the available evidence, we believe this management layer was used to execute commands across connected systems.

Our investigation remains ongoing, and additional safeguards have been implemented while analysis continues.

**Scope of Impact**

We utilize multiple independent platforms to operate our VPS services. At this time, we have confirmed that the incident was limited to nodes associated with a single management instance. Other infrastructure, platforms, and service regions were not impacted.

We do not store customer personal data or billing information within VPS management platforms. Our investigation has found no evidence that customer databases, billing systems, or other internal services were accessed or compromised.

We are currently finalizing recovery steps and next actions. All affected customers will be contacted directly via email with further information, and we sincerely apologize for the inconvenience this incident has caused.

We have identified an outage on our services, at this stage, some services should be facing *network timeouts*

Our network engineers and sysadmins are investigating the issue at the moment.