CloudConeReviews of cloudcone.com

Response from CloudConeFeb 6, 2026

We Are Truly Sorry We apologize for the impact this incident had on you, especially the data loss, downtime, and disruption to your services. We fully understand how frustrating this situation was, and we sincerely regret that your experience did not meet the level of reliability and communication you expect from us. What Happened As explained in our initial incident report (Please read here: https://app.cloudcone.com/incident-346624), a third-party VPS deployment platform was compromised through a vulnerability, which allowed unauthorized access to certain LA host nodes. This caused disk corruption on the affected nodes. Despite multiple recovery attempts, including raw device analysis and filesystem reconstruction, the data on these nodes was unfortunately irrecoverable. Only a subset of LA VPS nodes were impacted, and customer billing and personal data remained secure. Please note that the initial public report took time to finalize because the investigation was still ongoing. However, updates were continuously provided on our status page (https://status.cloudcone.com/) from the start of the incident so customers could stay informed in real time. Next Steps for Users During recovery, affected systems were isolated and rebuilt from a clean state. The impacted nodes are now ready for VPS re-installation, and once customers see the re-install banner in their control panel, it’s safe to proceed with rebuilding services and restoring any available backups. Due to the scale of the event, reinstallations were processed through a queue and typically took 3–6 hours to complete. Even though this incident was out of our control and isn’t eligible for standard SLA or compensation credits, our team is still reviewing cases to see if any compensation can be offered. Improvements Taken Following the incident, we rotated credentials, strengthened firewall and IP-level controls, rebuilt the deployment gateway, and began transitioning away from the affected third-party platform to our own in-house virtualization platform. We acknowledge the disruption this caused and sincerely apologize. This external attack will not bring us down. We are continuing to strengthen our infrastructure, enhance our incident response, and improve customer communication to better support our valued clients.

Response from CloudConeFeb 6, 2026

We Are Truly Sorry We apologize for the impact this incident had on you, especially the data loss, downtime, and disruption to your services. We fully understand how frustrating this situation was, and we sincerely regret that your experience did not meet the level of reliability and communication you expect from us. What Happened As explained in our initial incident report (Please read here: https://app.cloudcone.com/incident-346624), a third-party VPS deployment platform was compromised through a vulnerability, which allowed unauthorized access to certain LA host nodes. This caused disk corruption on the affected nodes. Despite multiple recovery attempts, including raw device analysis and filesystem reconstruction, the data on these nodes was unfortunately irrecoverable. Only a subset of LA VPS nodes were impacted, and customer billing and personal data remained secure. Please note that the initial public report took time to finalize because the investigation was still ongoing. However, updates were continuously provided on our status page (https://status.cloudcone.com/) from the start of the incident so customers could stay informed in real time. Next Steps for Users During recovery, affected systems were isolated and rebuilt from a clean state. The impacted nodes are now ready for VPS re-installation, and once customers see the re-install banner in their control panel, it’s safe to proceed with rebuilding services and restoring any available backups. Due to the scale of the event, reinstallations were processed through a queue and typically took 3–6 hours to complete. Even though this incident was out of our control and isn’t eligible for standard SLA or compensation credits, our team is still reviewing cases to see if any compensation can be offered. Improvements Taken Following the incident, we rotated credentials, strengthened firewall and IP-level controls, rebuilt the deployment gateway, and began transitioning away from the affected third-party platform to our own in-house virtualization platform. We acknowledge the disruption this caused and sincerely apologize. This external attack will not bring us down. We are continuing to strengthen our infrastructure, enhance our incident response, and improve customer communication to better support our valued clients.

Response from CloudConeFeb 6, 2026

We Are Truly Sorry We apologize for the impact this incident had on you, especially the data loss, downtime, and disruption to your services. We fully understand how frustrating this situation was, and we sincerely regret that your experience did not meet the level of reliability and communication you expect from us. What Happened As explained in our initial incident report (Please read here: https://app.cloudcone.com/incident-346624), a third-party VPS deployment platform was compromised through a vulnerability, which allowed unauthorized access to certain LA host nodes. This caused disk corruption on the affected nodes. Despite multiple recovery attempts, including raw device analysis and filesystem reconstruction, the data on these nodes was unfortunately irrecoverable. Only a subset of LA VPS nodes were impacted, and customer billing and personal data remained secure. Please note that the initial public report took time to finalize because the investigation was still ongoing. However, updates were continuously provided on our status page (https://status.cloudcone.com/) from the start of the incident so customers could stay informed in real time. Next Steps for Users During recovery, affected systems were isolated and rebuilt from a clean state. The impacted nodes are now ready for VPS re-installation, and once customers see the re-install banner in their control panel, it’s safe to proceed with rebuilding services and restoring any available backups. Due to the scale of the event, reinstallations were processed through a queue and typically took 3–6 hours to complete. Even though this incident was out of our control and isn’t eligible for standard SLA or compensation credits, our team is still reviewing cases to see if any compensation can be offered. Improvements Taken Following the incident, we rotated credentials, strengthened firewall and IP-level controls, rebuilt the deployment gateway, and began transitioning away from the affected third-party platform to our own in-house virtualization platform. We acknowledge the disruption this caused and sincerely apologize. This external attack will not bring us down. We are continuing to strengthen our infrastructure, enhance our incident response, and improve customer communication to better support our valued clients.

Response from CloudConeFeb 6, 2026

We Are Truly Sorry We apologize for the impact this incident had on you, especially the data loss, downtime, and disruption to your services. We fully understand how frustrating this situation was, and we sincerely regret that your experience did not meet the level of reliability and communication you expect from us. What Happened As explained in our initial incident report (Please read here: https://app.cloudcone.com/incident-346624), a third-party VPS deployment platform was compromised through a vulnerability, which allowed unauthorized access to certain LA host nodes. This caused disk corruption on the affected nodes. Despite multiple recovery attempts, including raw device analysis and filesystem reconstruction, the data on these nodes was unfortunately irrecoverable. Only a subset of LA VPS nodes were impacted, and customer billing and personal data remained secure. Please note that the initial public report took time to finalize because the investigation was still ongoing. However, updates were continuously provided on our status page (https://status.cloudcone.com/) from the start of the incident so customers could stay informed in real time. Next Steps for Users During recovery, affected systems were isolated and rebuilt from a clean state. The impacted nodes are now ready for VPS re-installation, and once customers see the re-install banner in their control panel, it’s safe to proceed with rebuilding services and restoring any available backups. Due to the scale of the event, reinstallations were processed through a queue and typically took 3–6 hours to complete. Even though this incident was out of our control and isn’t eligible for standard SLA or compensation credits, our team is still reviewing cases to see if any compensation can be offered. Improvements Taken Following the incident, we rotated credentials, strengthened firewall and IP-level controls, rebuilt the deployment gateway, and began transitioning away from the affected third-party platform to our own in-house virtualization platform. We acknowledge the disruption this caused and sincerely apologize. This external attack will not bring us down. We are continuing to strengthen our infrastructure, enhance our incident response, and improve customer communication to better support our valued clients.

Response from CloudConeFeb 6, 2026

We’re very sorry to hear about the issues you’ve had with your refund and account. Our goal is to make sure you’re completely satisfied with your experience at CloudCone, and we’d like the chance to make things right. Could you please share your ticket ID via the TP information request? Once we have it, we can investigate your refund request further and provide a more accurate response to your review. We look forward to your reply.

Response from CloudConeFeb 6, 2026

I’m truly sorry for the frustration and stress this has caused. 16 days without a reply is completely unacceptable, and we understand how upsetting this must be, especially given the trust you’ve placed in us. Our goal is to make sure you’re satisfied with your experience at CloudCone, and we want to make this right. Could you please share your ticket ID via the TP information request? Once we have it, we can immediately investigate your refund and server issues, and provide a more accurate response to your review. We look forward to your reply.