Safespring Status

All Systems Operational

Uptime over the past 90 days. View historical uptime.
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.

No incidents or maintenance related to this downtime.

Feb 7, 2026

No incidents reported today.

Feb 6, 2026
Safespring On-demand Kubernetes in Osl2
Completed - The scheduled maintenance has been completed.
Feb 6, 14:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 6, 13:00 CET
Scheduled - * Planned work: Updating bgp component
 * Impact: minimal
 * Customer actions needed: None
Feb 5, 09:03 CET
STO1: Reboot and Migration of L2 instances
Completed - The scheduled maintenance has been completed.
Feb 6, 09:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 5, 19:00 CET
Scheduled - 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.
Jan 29, 14:18 CET
Feb 5, 2026
Single DCO hypervisor impacted by libvirtd lockup
Resolved - This incident has been resolved.
Feb 5, 10:27 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 4, 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 4, 16:26 CET
Update - We are currently live migrating instances from the problematic node to other hypervisors.
Feb 4, 16:13 CET
Investigating - We are currently investigating this issue.
Feb 4, 16:05 CET
Feb 4, 2026
Feb 3, 2026

No incidents reported.

Feb 2, 2026

No incidents reported.

Feb 1, 2026

No incidents reported.

Jan 31, 2026

No incidents reported.

Jan 30, 2026

No incidents reported.

Jan 29, 2026
Hypervisor drive failure in RISE private cloud
Resolved - The hypervisor has been disabled and all instance owners has been informed.
Jan 29, 14:13 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 29, 11:45 CET
Investigating - We are currently investigating this issue.
Jan 29, 11:07 CET
Jan 28, 2026

No incidents reported.

Jan 27, 2026

No incidents reported.

Jan 26, 2026

No incidents reported.

Jan 25, 2026

No incidents reported.

Jan 24, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage