Safespring Status

All Systems Operational

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

Third attempt of move of Backup service Jun 2, 2025 10:00-16:00 CEST

The important part has been to evacuate the current hardware, and we have tried to move the complete service, now we will only move it to another server nearby, an operation that has been done before and which does not require full synchronization of database and client data.
This means it will be faster, even if it might still take "a few hours". We reserve 6 hours from 10.00 on June 2nd, but expect it to be finished hours before the maintenance window expires. We will also patch the operating system and server software while the service is down. As previous maintenances, please reschedule backups if your scheme is set for daytime (most are at night) and you cannot delay or miss this one day. This time, the IP addresses will not change.
Posted on May 26, 2025 - 16:04 CEST
Jun 1, 2025

No incidents reported today.

May 31, 2025

No incidents reported.

May 30, 2025

No incidents reported.

May 29, 2025

No incidents reported.

May 28, 2025
Issues with STO1 compute service
Resolved - This incident has been resolved.
May 28, 16:01 CEST
Monitoring - We have found the problem and applied a fix. We are now monitoring again.
May 28, 13:28 CEST
Investigating - We still see some issues with block storage and have started to investigate again.
May 28, 12:57 CEST
Monitoring - A fix has been implemented and we are monitoring the results.
May 28, 10:57 CEST
Investigating - We are currently investigating a possible issue with Safespring Compute. We will continue to post updates until the issue is resolved.
This is an effect of the block storage hardware issue we had earlier this morning.
May 28, 09:52 CEST
Degraded block storage performance in STO1
Resolved - This incident has been resolved.
May 28, 10:56 CEST
Monitoring - Storage cluster should be back up and working now, we will continue monitoring it for a while.
May 28, 09:15 CEST
Update - We are continuing to work on block storage cluster, updates will follow
May 28, 08:56 CEST
Identified - We've identified the cause as a hardware failure and are working to mitigate the impact
May 28, 08:21 CEST
Investigating - We are currently investigating an issue with the block storage cluster in STO1, causing volume operations to fail.
May 28, 07:48 CEST
May 27, 2025

No incidents reported.

May 26, 2025

No incidents reported.

May 25, 2025

No incidents reported.

May 24, 2025

No incidents reported.

May 23, 2025

No incidents reported.

May 22, 2025
Second attempt to move Backup service
Completed - Even though we sidestepped a few of the things that we think made it too slow the last time, it still took too long to completely sync both client data and the index-database in a day, so I am aborting the move now, we will not overshoot the announced timeframe this time.
We are now restarting the service in the former location with the old IP, and making differerent and hopefully better plans for migrating client data in a safe and secure manner.
While we are sorry for not succeeding this time either, the integrity of the backups is our primary concern and we will not take any chances or shortcuts that induce risk to them.
May 22, 14:54 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 22, 09:00 CEST
Scheduled - Backup server needs to move and we will try again next Thursday, this time a bit better prepared for the complexities of it. As before, please reschedule backups so they finish before 09.00 or start after 17.00 for this day as needed. If your clients normally run in the evening/nights and finish before 09 or one missed daytime backup is acceptable, no actions are needed.

DNS name and certificate stays the same, but for sites with hardcoded firewall rules, the new ips for the service will be: 192.121.133.88 and 2a09:d400:1:40::19c

We are grateful for your patience.
May 14, 16:55 CEST
May 21, 2025

No incidents reported.

May 20, 2025

No incidents reported.

May 19, 2025

No incidents reported.

May 18, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage