Single DCO hypervisor impacted by libvirtd lockup

Incident Report for Safespring

Monitoring

A fix has been implemented and we are monitoring the results.
Posted Feb 04, 2026 - 18:09 CET

Identified

Live migration of instances from problematic hypervisor is stuck due to libvirtd being unresponsive. We are proceeding with a reboot of the hypervisor to recover the host. Instances running on this host experience a short downtime during the reboot.
Posted Feb 04, 2026 - 16:26 CET

Update

We are currently live migrating instances from the problematic node to other hypervisors.
Posted Feb 04, 2026 - 16:13 CET

Investigating

We are currently investigating this issue.
Posted Feb 04, 2026 - 16:05 CET
This incident affects: Safespring Private Cloud.
← Current Status Powered by Atlassian Statuspage