Monitoring - A fix has been implemented and we are monitoring the results.
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.
Feb 04, 2026 - 16:26 CET
Update - We are currently live migrating instances from the problematic node to other hypervisors.
Feb 04, 2026 - 16:13 CET
Investigating - We are currently investigating this issue.
Feb 04, 2026 - 16:05 CET
Safespring Compute
Operational
90 days ago
99.49
% uptime
Today
Safespring Storage
Operational
90 days ago
99.99
% uptime
Today
Safespring Backup
Operational
90 days ago
99.49
% uptime
Today
Safespring Private Cloud
Operational
90 days ago
99.48
% uptime
Today
Safespring Portal
Operational
90 days ago
100.0
% uptime
Today
On-demand Kubernetes
Operational
90 days ago
100.0
% uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
As part of our ongoing infrastructure migration, we are rescheduling the maintenance window that was previously planned for January 27, 2026, but later cancelled. Maintenance Window: Start: Thursday, February 5th, 2026 at 19:00 End: Friday, February 6th, 2026 at 09:00 Who is affected: This maintenance only applies to instances using L2 flavors. Self-Service Reboot Option: If you prefer to reboot your L2 instances yourself before the maintenance window, please follow these instructions: Power off the virtual machine and wait until OpenStack shows a SHUTOFF state Power up the virtual machine again Email support@safespring.com with the instance ID(s) you have rebooted Important: This process is only required for L2 flavors, and a normal reboot is not sufficient. If you have any questions or experience any unexpected behavior, please contact us at support@safespring.com. Posted on
Jan 29, 2026 - 14:18 CET
Past Incidents
Feb 5, 2026
No incidents reported today.
Feb 4, 2026
Unresolved incident: Single DCO hypervisor impacted by libvirtd lockup.
Completed -
The scheduled maintenance has been completed.
Jan 23, 14:00 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 16, 10:00 CET
Scheduled -
We will be performing a scheduled migration of services from our current hypervisors to upgraded hardware. This maintenance window will run from 2026-01-16 through 2026-01-23.
This migration will be performed using live migration technology, which allows us to move services while they remain operational. You should not experience any downtime or interruption to your services during this period.
Instances that use local disks may require a single reboot to complete the migration successfully. If your instance is affected, we will notify you at least one day in advance and schedule the reboot outside of business hours. If you prefer to reboot your instance yourself at a time that suits you, please contact us for instructions.
While we do not anticipate any impact, please contact us immediately if you notice any unexpected behavior or performance changes during the maintenance window:
We appreciate your patience as we complete this infrastructure improvement. If you have any questions, please don't hesitate to reach out.
Jan 16, 09:53 CET