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
100.0 % 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

Short service interruption for OpenStack in RISE1 Sep 24, 2025 13:00-15:00 CEST

As part of a broader upgrade activity, we will be performing maintenance on the OpenStack control plane databases in RISE1 on September 24 between 13:00 and 15:00. Running instances will not be affected, but the Horizon dashboard and the Compute service API may be unavailable for up to the duration of the maintenance window.

Customer action required: none.
Posted on Sep 17, 2025 - 09:37 CEST

OpenStack upgrade RISE1 Sep 25, 2025 08:00-17:00 CEST

We will be upgrading the OpenStack platform in RISE1 on September 25 between 8:00 and 17:00

All instances will remain up and running throughout the maintenance. However, the API and dashboard may be temporarily unavailable or unreliable at times.
The S3 API in RISE1 will also be affected due to the integration with OpenStack authentication.

Customer action required: none.
Posted on Sep 17, 2025 - 09:40 CEST

Planned Reboot of l2 Instances in RISE1 Following OpenStack Upgrade Sep 26, 2025 10:00-12:00 CEST

Following the OpenStack upgrade, we need to reboot l2-type instances in RISE1 on September 26 between 10:00 and 12:00. This will only happen once, and the instances will be immediately available again after the restart.

Please note that the maintenance window reflects the period during which the restart will take place, not the actual downtime for customers. The downtime itself will typically be no more than a couple of minutes.

Customer action required:
If you have any unsaved work or configuration changes that need to be made in advance, please ensure these are completed before the start of the maintenance window. If you have services that require manual startup, please set aside time after the maintenance window to perform this.
Posted on Sep 17, 2025 - 09:46 CEST
Sep 18, 2025

No incidents reported today.

Sep 17, 2025

No incidents reported.

Sep 16, 2025

No incidents reported.

Sep 15, 2025

No incidents reported.

Sep 14, 2025

No incidents reported.

Sep 13, 2025

No incidents reported.

Sep 12, 2025
Planned Reboot of l2 Instances in OSL2 Following OpenStack Upgrade
Completed - The scheduled maintenance has been completed.
Sep 12, 11:17 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 12, 10:00 CEST
Scheduled - Following the OpenStack upgrade, we need to reboot the l2-type instances in OSL2. This will only happen once, and the instances will be immediately available again after the restart.

Please note that the maintenance window reflects the period during which the restart will take place, not the actual downtime for customers. The downtime itself will typically be no more than a couple of minutes.

Customer action required:
If you have any unsaved work or configuration changes that need to be made in advance, please ensure these are completed before the start of the maintenance window. If you have services that require manual startup, please set aside time after the maintenance window to perform this.
Sep 4, 10:09 CEST
Sep 11, 2025
Openstack upgrade OSL2
Completed - The scheduled maintenance has been completed.
Sep 11, 13:30 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 11, 08:00 CEST
Update - We will be undergoing scheduled maintenance during this time.
Sep 4, 09:28 CEST
Scheduled - We will be upgrading the OpenStack platform in OSL2 on September 11 between 8:00 and 17:00

All instances will remain up and running throughout the maintenance. However, the API and dashboard may be temporarily unavailable or unreliable at times.
The S3 API in OSL2 will also be affected due to the integration with Openstack authentication.

No customer actions are needed.
Sep 4, 09:27 CEST
Sep 10, 2025

No incidents reported.

Sep 9, 2025

No incidents reported.

Sep 8, 2025

No incidents reported.

Sep 7, 2025

No incidents reported.

Sep 6, 2025
rise1 compute host r/o filesystem
Resolved - This incident has been resolved.
Sep 6, 18:19 CEST
Monitoring - A fix has been implemented and we are monitoring the results.
Sep 6, 13:19 CEST
Update - unfortunately the affected drive vanished after a reboot, which means we are not unable to recover the localdrive (l2. flavor) instances on this host.
b2 flavored instances are booted back up and are being migrated to other compute hosts.
Sep 6, 13:19 CEST
Update - copying files consitantly failed, so we are skipping that and trying to reboot the host
Sep 6, 12:29 CEST
Update - we are currently trying to copy the instances' data over to a working compute host, this will at the current speed take around 70 minutes.

following that we will do a reboot of the affected host to see if that will make it possible to get the drive back to a r/w state so we can migrate off.

if that does not work we will attempt recreating instances on other hosts manually.
Sep 6, 12:14 CEST
Identified - one of the compute hosts in the rise1 site has issues with its local drives. instances using these drives will not be able to write to them.
Sep 6, 11:44 CEST
Sep 5, 2025

No incidents reported.

Sep 4, 2025
We had Issues with Block Storage in sto4 but it is fine now and currently monitoring
Resolved - The service has been stable since last update.This incident has been resolved.
Sep 4, 15:12 CEST
Update - There was an issue during a routine reweighting of block storage devices which caused a short break in storage accessibility in sto4 around 10:40 cest. the reweight operation was stopped and we are currently investigating what happened. storage performance should currently be back to normal.
Sep 4, 12:17 CEST
Monitoring - A fix has been implemented and we are monitoring the results.
Sep 4, 12:15 CEST
← Incident History Powered by Atlassian Statuspage