← Go back to Civo Ltd

Service disruption NYC1

May 1, 2024 at 9:40 PM


Resolved after 4h 24m . May 2, 2024 at 2:04 AM

2024-05-02 02:04:00 UTC

We believe the remaining affected workloads are restored and we are continuing to monitor their stability.

2024-05-02 01:41:00 UTC

The vast majority of workloads are back up and running as normal. We are working on restoring the remaining ones and monitoring the platform for stability.

2024-05-02 01:15:00 UTC

work continues with restoring affected pods, VMs and other resources in NYC1. We are currently hoping to have this work finished off in the next half an hour or so.

2024-05-02 00:45:00 UTC

we are seeing the count of affected resources decrease but are still working on the wider issue. We will next update in half an hour.

2024-05-02 00:15:00 UTC

Work is progressing on restoring the remaining workloads that are affected. Next update within 30 minutes

2024-05-01 23:45:00 UTC

the work to recover the affected virtual machines and Kubernetes clusters is ongoing.

2024-05-01 23:15:00 UTC

We are continuing with recovery of affected workloads. We are going to issue the next update within 30 minutes.

2024-05-01 22:45:00 UTC

We are still working on restoring affected services to full functionality. While this is progressing well, we expect the process to continue to take some time. We will next update within 30 minutes (23:15 UTC).

2024-05-01 22:15:00 UTC

Affected workloads are being restored and the recovery process looks stable. We will keep this status page updated while we continue the process. We expect to post the next update within 30 minutes (22:45 UTC)

2024-05-01 22:00:00 UTC

We are working on restoring the workloads affected, and will update at the latest in 20 minutes (22:20 UTC)

2024-05-01 21:58:00 UTC

The team is investigating the root cause of the disruption and is working to bring any halted workloads back online.

2024-05-01 21:40:00 UTC

A subset of cloud resources (Kubernetes clusters, instances, etc) may be inaccessible in NYC1 at the moment and we are investigating the cause. Most workloads in the NYC1 region remain unaffected and respond as normal. New resource launches should not be seeing issues.