Scheduled Singapore VPS maintenance on 18 Oct 2026 01:27:10 (UTC+01:00)
In progress on 21 Oct 2026 03:55:38 (UTC+01:00)
We’ve made substantial progress with the scheduled security maintenance. Services have been restored following the completed restarts, with follow-up work and verification continuing.

We’ll provide a further update once maintenance has concluded. If you’re experiencing any issues with your VPS, please contact our support team so we can investigate.

Thank you for your patience during this maintenance.
Scheduled on 18 Oct 2026 01:54:49 (UTC+01:00)
Sunday 18 October 2026, 02:00 BST (01:00 UTC), until Tuesday 20 October 2026, 02:00 BST (01:00 UTC).

We are carrying out urgent security maintenance to address CVE-2026-99999 across our VPS platform. We expect to finish much sooner than the end of this window, but have allowed extra time for checks and recovery work if needed.

VPSs may be shut down and restarted as we work through the hosts in stages. Restarts generally take a few minutes, although maintenance and verification can take longer. We will use controlled shutdowns and check each host before and after its restart.

Progress updates will be posted here. This replaces the previously announced Singapore maintenance window for 20 October.
Scheduled on 18 Oct 2026 01:27:10 (UTC+01:00)
Tuesday 20 October 2026, 01:00–05:00 SGT (UTC+8).
Monday 19 October 2026, 17:00–21:00 UTC.

We will upgrade sg-hv133 and sg-hv140 to Debian 13, apply security updates for CVE-2026-99999 and install KernelCare for ongoing kernel patching.

VPSs on these two hosts will be shut down cleanly while their host is upgraded and restarted. Please allow for service interruption throughout the window. We will work through the hosts one at a time and post updates here as the work progresses.

The operating systems installed inside the VPSs and their IP addresses will remain unchanged. Affected customers have been emailed a list of their VPSs included in this maintenance.
Amsterdam Connectivity Issues on 27 Mar 2026 01:15:59 (UTC+01:00)
Resolved
Mar 26th 22:08 UTC - We are currently experiencing connectivity issues affecting our Amsterdam region due to multiple simultaneous backbone fibre cuts. We apologise for the disruption and are working to resolve this as quickly as possible.

Mar 26th 22:25 UTC - The fibre vendor has identified the cause of the multiple diverse fibre cuts impacting AMS1 connectivity. We are currently working with the vendor on an alternative fibre solution to restore service. We will provide a further update as soon as more information is available.

Mar 27th 00:01 UTC - We have implemented a temporary fix and AMS1 connectivity is now restored.
Network Outage - Los Angeles on 7 Feb 2026 04:59:48 (UTC+01:00)
Resolved on 7 Feb 2026 05:00:28 (UTC+01:00)
02:31 UTC - We are currently experiencing a network outage affecting our Los Angeles location. The issue has been identified as originating with an upstream network provider. Our team has escalated this with the provider, and it is being treated as a critical incident. We are actively monitoring the situation and will post updates as more information becomes available.

03:50 UTC - This has now been resolved. We are working to ascertain the exact cause with the network supplier, as the issue was within their network.
Update on 7 Feb 2026 05:00:23 (UTC+01:00)
02:31 UTC - We are currently experiencing a network outage affecting our Los Angeles location. The issue has been identified as originating with an upstream network provider. Our team has escalated this with the provider, and it is being treated as a critical incident. We are actively monitoring the situation and will post updates as more information becomes available.

03:50 UTC - This has now been resolved. We are working to ascertain the exact cause with the network supplier, as the issue was within their network.
Identified on 7 Feb 2026 04:59:48 (UTC+01:00)
02:31 UTC - We are currently experiencing a network outage affecting our Los Angeles location. The issue has been identified as originating with an upstream network provider. Our team has escalated this with the provider, and it is being treated as a critical incident. We are actively monitoring the situation and will post updates as more information becomes available.

We apologize for the disruption and appreciate your patience.

Next update will be posted as soon as new information is available from our upstream provider.