CloudConeReviews of cloudcone.com

Response from CloudConeFeb 20, 2026

We sincerely apologize to you & everyone affected, and completely understand that losing data is incredibly frustrating. We published an official incident report explaining what happened, what systems were affected, and the steps taken to contain and resolve it. You can review the full statement here: https://app.cloudcone.com/incident-346624 As part of our commitment to supporting customers after the incident, we introduced these measures: Credit Compensation Based on Customer Feedback: All impacted customers automatically received account credits equivalent to one full month of their VPS package. For example, a VPS billed at $60 per year would receive $5 in account credits added directly to the account balance. Service Extensions: Affected servers will automatically receive a free two-month service extension at each of the next two renewals, for a total of 4 free months of service. For example, a standard 12-month annual renewal will be extended to 14 months at no additional cost. Updated due dates will be applied automatically as renewals occur. Discounted Monthly Backups: In Q2 2026, affected customers will receive 50% off monthly server backups for up to one year on the upcoming platform. This initiative aims to strengthen long-term data protection and provide additional peace of mind. We also want to address the concern about this “..will do same in future”. Since the incident, we’ve made structural improvements to the platform and strengthened security controls specifically to reduce future risk. Incidents like this are taken extremely seriously, and significant changes were made as a result. -Clean reinstallation of the VPS deployment gateway and affected host nodes. -Rotation of all API keys and sensitive credentials. -Additional hardening of IP-level access controls and firewall rules. Platform Improvements: Our Budget VPS instances are scheduled to be migrated to CloudCone’s new in-house platform, which was already in final testing and is expected to launch by the end of March. The new platform is designed to deliver improved reliability, performance, and enhanced security. We respect your decision to move to another provider and genuinely wish you success there. At the same time, our focus remains clear: learning from the incident, strengthening our systems, and earning back customer trust through real actions, not just words. We truly value every one of you.

Response from CloudConeFeb 9, 2026

We are truly sorry for the impact this incident has had on you and your work. Losing 5 years of backups and 8 years of accumulated data is devastating, and we fully understand the seriousness of the situation. We acknowledge that you trusted our service to securely host and protect your data, and we regret that we failed to meet that trust. We understand that this has disrupted your livelihood, and we are deeply sorry for the consequences this has caused. 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. 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 9, 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. 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 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.