CloudCone had 6 outages in the last 2 years totaling 346h 30m of downtime — averaging 0.2 incidents per month.
There were 6 CloudCone outages since May 14, 2026 totaling 346h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.
We have identified an outage some of our VPS nodes, Virtual instances on this specific node should see network timeouts. Our network engineers and sysadmins are investigating the issue at the moment. Further findings and updates will be updated on this status page.
Incident has ben resolved
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. Further findings and updates will be updated on this status page.
The core issue is isolated to the upstream DWDM connections. The upstream providers are looking into the issue at the moment.
Services have been taken online via redundant measures. Network has been switched to GRE tunnelling, customers may experience degraded network performance, however it’ll keep traffic flowing until the provider resolves the core issue with the DWDM connections. We are also awaiting secondary DWDM uplink from our upstream providers to prevent such issues in the future. Currently the network is being closely monitored
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.
Services have been restored
Our network is experiencing intermittent timeouts on the SC2 services. Our initial investigation shows that the problem appears to be isolated on the new DC (LAX) at the moment. Our engineers are working on a fix
There is a network outage happening at the moment. Our network engineers are looking into the issue at the moment
Services should be reachable now
We have identified an outage on our services, at this stage, some services should be facing network timeouts and degraded performance. Our network engineers and sysadmins are investigating the issue at the moment. Further findings and updates will be updated on this status page.
All affected hypervisors are back online.
We have identified RAID outage on our S160-V node in Los Angeles DC, Virtual instances on this specific node should see network timeouts. Our network engineers and sysadmins are investigating the issue at the moment. Further findings and updates will be updated on this status page.
The RAID 10 array could not be recovered despite recovery attempts. The node has now been brought back online to allow customers to proceed with restoring their data from backups after re-installing the VM. Customers are advised to begin the restoration process at their earliest convenience.