Safespring Status

All Systems Operational

Uptime over the past 90 days. View historical uptime.
Safespring Compute Operational
90 days ago
99.95 % uptime
Today
Safespring Storage Operational
90 days ago
100.0 % uptime
Today
Safespring Backup Operational
90 days ago
99.99 % uptime
Today
Safespring Private Cloud Operational
90 days ago
99.97 % 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.

Scheduled Maintenance

OpenStack upgrade STO4 Nov 8, 2025 09:00-17:00 CET

We will be upgrading the OpenStack platform in STO4 on November 8 between 9:00 and 17:00

All instances will remain up and running throughout the maintenance. However, the API, dashboard and S3 API may be temporarily unavailable or unreliable at times between 9:00 and 12:00
Posted on Oct 15, 2025 - 11:37 CEST

STO3 S3 Archive Cluster Decommissioning. Nov 24, 2025 12:00-13:00 CET

Safespring will be decommissioning the S3 archive cluster in STO3.

On October 6, we already updated the DNS records for *.s3.sto3.safedc.net to point to our new cluster.

Over the past few weeks, we have monitored the migration and confirmed that all customer traffic has successfully moved to the new cluster.

We are now preparing to decommission the old cluster during the last week of November.

If you have any questions, please don’t hesitate to contact us.
Posted on Nov 03, 2025 - 14:52 CET
Nov 4, 2025

No incidents reported today.

Nov 3, 2025

No incidents reported.

Nov 2, 2025

No incidents reported.

Nov 1, 2025

No incidents reported.

Oct 31, 2025

No incidents reported.

Oct 30, 2025

No incidents reported.

Oct 29, 2025
Backup admin portal restart
Completed - The scheduled maintenance has been completed.
Oct 29, 18:15 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 29, 18:00 CET
Scheduled - We will be restarting the client administration portal for the Backup service at 18:00 for security improvements (removing older algorithms from proposed list). No impact on backups or restores. No customer action required.
Oct 29, 14:06 CET
Oct 28, 2025
Issues with backup portal login
Resolved - This incident has been resolved.
Oct 28, 15:41 CET
Update - We are continuing to monitor for any further issues.
Oct 28, 15:41 CET
Monitoring - The issue has been identified immediately and fixed.
Oct 28, 14:32 CET
Investigating - We are investigating an issue with backup portal login issues.
Oct 28, 14:21 CET
Oct 27, 2025

No incidents reported.

Oct 26, 2025

No incidents reported.

Oct 25, 2025

No incidents reported.

Oct 24, 2025

No incidents reported.

Oct 23, 2025
Issues with backup
Resolved - This incident has been resolved.
Oct 23, 12:15 CEST
Update - Issue resolved. Please re-run any TSM backups that failed during tonight’s schedule.
Oct 23, 09:15 CEST
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 23, 09:07 CEST
Identified - The issue has been identified and a fix is being implemented.
Oct 23, 09:02 CEST
Investigating - Some customers are experiencing issues with their TSM clients reporting the error “ANS1311E Server out of data storage space.” It appears that the backup server is not utilizing all of the space allocated to it. We are working to resolve the issue as quickly as possible and apologize for any inconvenience.
Oct 23, 08:49 CEST
Oct 22, 2025

No incidents reported.

Oct 21, 2025
Network performance issues in Osl2
Resolved - This incident has been resolved.
Oct 21, 15:27 CEST
Monitoring - Reboot of compute node fixed the issue and we are able to live-migrate instance off from problematic node to other hypervisor. Monitoring the status now.
Oct 21, 13:22 CEST
Update - We are doing an emergency reboot of problematic compute node in osl2 to fix the libvirt issue. VMs running on this host will be affected.
Oct 21, 13:02 CEST
Investigating - Issue with libvirtd lock handling is back again and we are currently investigating this.
Oct 21, 12:50 CEST
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 21, 11:40 CEST
Identified - The issue has been identified as libvirtd service acted up in one of the compute nodes in osl2. Fix has been implemented and we are currently monitoring the status.
Oct 21, 10:33 CEST
Investigating - We are currently investigating this issue.
Oct 21, 09:55 CEST
← Incident History Powered by Atlassian Statuspage