Safespring Status
Investigating - From January 2022, we are deprecating the old ipnett.no and ipnett.se domains.

All new sites will use adresses in safespring.com domain for web console, and adresses in the safedc.net domain for api access.

The legacy sites will be available on

dashboard.cloud.sunet.se in Sweden and
login.osl1.safespring.com in Norway.

If you use API access for compute in the old sites, you will have to point to the adresses using /etc/hosts (or similar).

Contact support@safespring.com if you have any questions
Jan 3, 10:34 CET
Investigating - No Safespring services are impacted, but we advice our customers to assess the impact to their own systems. We have posted an update regarding the log4j on our blog: https://www.safespring.com/blogg/security-advisory-2021/
Dec 13, 12:26 CET
Safespring Compute Operational
90 days ago
100.0 % uptime
Today
Safespring Storage Operational
90 days ago
99.99 % uptime
Today
Safespring Backup Operational
90 days ago
100.0 % uptime
Today
Safespring Private Cloud 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.
Past Incidents
Jan 17, 2022

No incidents reported today.

Jan 16, 2022

No incidents reported.

Jan 15, 2022

No incidents reported.

Jan 14, 2022

No incidents reported.

Jan 13, 2022

No incidents reported.

Jan 12, 2022

No incidents reported.

Jan 11, 2022
Resolved - This incident has been resolved.
Jan 11, 16:40 CET
Update - We are continuing to work on a fix for this issue.
Jan 11, 11:52 CET
Identified - We are investigating a hardware issue with one of our backupservers. Clients that back up to tsm1.cloud.safedc.net are affected.
Jan 11, 11:52 CET
Update - We are continuing to investigate this issue.
Jan 11, 08:44 CET
Investigating - We are currently investigating a possible issue with Safespring Backup. We will continue to post updates until the issue is resolved.
Jan 11, 08:42 CET
Resolved - This incident has been resolved.
Jan 11, 12:11 CET
Update - We are continuing to work on the backend to increase the performance and stability of the cluster. This means running a rebalance task which takes time. To ensure the stability we let the rebalance task work slowly while we are closely monitoring the cluster.
Nov 22, 14:05 CET
Update - The cluster is recovering slowly. Still some misplaced and degraded objects but we will not make any changes to make things recover faster until Monday. Next update will be around noon on Monday or when we see other needs of update.
Nov 21, 18:55 CET
Update - The service has slowly recovered during the night and is working as expected. There might be some performance degradation since there's still data integrity checks ongoing. The root cause analyzes and monitoring continues. Status updates will be made if there's any changes with the cluster.
Nov 20, 09:24 CET
Monitoring - The cluster is now open for read/write access but still under monitoring. In case of any new issues it might be shut down again. We'll keep a close look at things until we can say it's fully recovered. Next update is not until tomorrow unless anything dramatically changes.
Nov 19, 20:57 CET
Update - We are still analyzing things and added more resources investigating this. Write is still blocked until we know more.
Nov 19, 18:25 CET
Update - Even though the cluster is in an ok state now, in order to find the culprit of the problem we have kept the access to the service down. We are right now working hard to be able to enable the service again.
Nov 19, 16:42 CET
Update - Recovery of the cluster at STO3 to a stable state is going forward. We still have to wait a bit to enable traffic from the outside again to ensure the stability in the cluster when it comes back. Sorry for the inconvenience.
Nov 19, 13:53 CET
Update - We are continuing to work on the issue. We have performed some operations to get the cluster in a stable state and the operations are working. We still have shutdown the S3 frontend to ensure the stability before we let on customer traffic. We will update here again at 14:00 the latest.
Nov 19, 12:32 CET
Update - We are continuing to investigate this issue.
Nov 19, 12:11 CET
Investigating - We have an incident in the STO3 storage site at the moment that we are working hard to fix. All incoming traffic is blocked at the moment. We will update here with new information at 13:00 at the latest.
Nov 19, 11:54 CET
Jan 10, 2022

No incidents reported.

Jan 9, 2022

No incidents reported.

Jan 8, 2022

No incidents reported.

Jan 7, 2022

No incidents reported.

Jan 6, 2022
Resolved - Networking glitch, fixed.
Jan 6, 10:12 CET
Investigating - We are currently investigating a possible issue with Safespring Compute. We will continue to post updates until the issue is resolved.
Jan 6, 10:05 CET
Jan 5, 2022
Resolved - Monitoring scripts reacting to the move away from cloud.ipnett.no/.se domains.
More information about this move at https://docs.safespring.com/service/known_issues/#cloudipnettnose-domains
Jan 5, 10:43 CET
Investigating - We are currently investigating a possible issue with Safespring Compute. We will continue to post updates until the issue is resolved.
Jan 5, 10:39 CET
Jan 4, 2022

No incidents reported.

Jan 3, 2022

Unresolved incident: Deprecation of ipnett domains.