Singapore Node Failure on 24 Sep 2026 14:20:22 (UTC+00:00)
Update on 4 Oct 2026 20:00:18 (UTC+00:00)
Update: 05/10/2026 01:17AM
We regret to inform that we were not able to recover any data from the server.
As mentioned by our technician and seen in photos, there was very major issue with the MB, and signs of smoke and carbon build up on components around, and another major factor that burnt area was near dimms, almost all of the dimms are wasted and about half of the NVMe disks are not showing up in replacement server.
After multiple tries, our technician was not able to recover the data from the limited working NVMe disks left. Sadly the charges in Singapore for everything is quite high, and we cannot continue to try further when our technician is not very positive about this situation now.
We're really sorry about this whole situation, however this is very rare case (first ever with us). The only possible solution in such cases is backup, so please take backups whenever you can. We provide backups, free and paid options both for more slots, so always backup, it just takes one click.
Update: 05/10/2026 01:17AM
We regret to inform that we were not able to recover any data from the server.
As mentioned by our technician and seen in photos, there was very major issue with the MB, and signs of smoke and carbon build up on components around, and another major factor that burnt area was near dimms, almost all of the dimms are wasted and about half of the NVMe disks are not showing up in replacement server.
After multiple tries, our technician was not able to recover the data from the limited working NVMe disks left. Sadly the charges in Singapore for everything is quite high, and we cannot continue to try further when our technician is not very positive about this situation now.
We're really sorry about this whole situation, however this is very rare case (first ever with us). The only possible solution in such cases is backup, so please take backups whenever you can. We provide backups, free and paid options both for more slots, so always backup, it just takes one click.
Identified on 24 Sep 2026 14:20:22 (UTC+00:00)
We’re aware of the node failure in Singapore, unfortunately the node blew up, and there was quite alot of smoke accordingly to our technician. This node is now considered fire hazard and cannot be kept in rack.
We’re working with supplier to source new node of same specifications. However it will take sometime. According to our upstream technician, it is very likely that other components in the server is also dead in this case. However we will still try to recover whatever is possible.
If you have backups, please open a ticket and our team will restore your vps on different node. If you dont, sadly we will have to wait for new hardware to try any kind of recovery if possible at all.
At this point, we are still planning on best way possible to check components and recover the data. We're working closely with our upstream, RH technician and supplier to sort out this situation as soon as possible. We will update here once we have more news on this case.
We’re aware of the node failure in Singapore, unfortunately the node blew up, and there was quite alot of smoke accordingly to our technician. This node is now considered fire hazard and cannot be kept in rack.
We’re working with supplier to source new node of same specifications. However it will take sometime. According to our upstream technician, it is very likely that other components in the server is also dead in this case. However we will still try to recover whatever is possible.
If you have backups, please open a ticket and our team will restore your vps on different node. If you dont, sadly we will have to wait for new hardware to try any kind of recovery if possible at all.
At this point, we are still planning on best way possible to check components and recover the data. We're working closely with our upstream, RH technician and supplier to sort out this situation as soon as possible. We will update here once we have more news on this case.
IPv6 Outage in Multiple Locations on 26 Dec 2025 08:56:29 (UTC+00:00)
Resolved on 8 Jan 2026 18:08:37 (UTC+00:00)
New IPv6 in West Midlands, UK is online now. New subnet is: 2401:8360:a3::/48
We are still working on remaining locations.
New IPv6 in West Midlands, UK is online now. New subnet is: 2401:8360:a3::/48
We are still working on remaining locations.
Resolved on 2 Jan 2026 23:22:21 (UTC+00:00)
IPv6 in Tampa, USA is back online. New subnet is: 2401:8360:f::/48
There is no longer IPv6 outage in any location, however we will still replace and use our own APNIC IPv6 /48s on other locations.
IPv6 in Tampa, USA is back online. New subnet is: 2401:8360:f::/48
There is no longer IPv6 outage in any location, however we will still replace and use our own APNIC IPv6 /48s on other locations.
Monitoring on 27 Dec 2025 09:09:51 (UTC+00:00)
IPv6 in London, UK is back online. New subnet is: 2401:8360:a2::/48
We're still working on other locations, things are progressing slow because of the holidays.
IPv6 in London, UK is back online. New subnet is: 2401:8360:a2::/48
We're still working on other locations, things are progressing slow because of the holidays.
In progress on 26 Dec 2025 08:56:29 (UTC+00:00)
We are aware of the outage in multiple locations caused by human error with our old IP supplier, and not getting any response because of the holidays. Thus we have decided to move away and use our own APNIC IPv6 /48s on every location so we have more control over our network.
We are aware of the outage in multiple locations caused by human error with our old IP supplier, and not getting any response because of the holidays. Thus we have decided to move away and use our own APNIC IPv6 /48s on every location so we have more control over our network.