DBaaS, Kubernetes, OpenStack
February 12, 2025 18:57 CET
February 12, 2025 17:57 UTC
[Investigating] Degraded Performance
We are currently seeing nightly disturbances in the API for v1 volumes in the STO1 availability zone.
This occurs every night between 19:00 and 02:00 CET.
Impact is inability to manage v1 volumes in STO1 during this time, impacted tasks is creation, deletion and attach/detach of volumes. There is NO impact on performance or availability of already attached volumes.
We are actively working with our storage vendor to correct this issue.March 5, 2025 09:53 CET
March 5, 2025 08:53 UTC
[Identified] Degraded Performance
We have made progress with our storage-vendor in mitigating the effects of the issue, reducing the time-window and impact it is causing.
Still we have no performance-impact but still (very) limited issues with volume-tasks (creation/deletion/attach&detach).October 14, 2025 07:56 CEST
October 14, 2025 05:56 UTC
[Identified] Degraded Performance
At the moment we are experiencing further issues with management of the V1 storage platform in STO1. We are invesigating work arounds until we have a sustainable fix to the underlying problem.October 14, 2025 10:01 CEST
October 14, 2025 08:01 UTC
[Identified] Partial Service Disruption
As the impact of the incident is affecting management of V1-volumes in STO1 we want to be transparent and inform that any changes, modifications, attach and detach of volumes of this type will not function and we strongly advice against any such operations at the moment.
This is limited to AZ: STO1 and the following volume-types:
v1-dynamic-40
16k-IOPS-enc
8k-IOPS-enc
4k-IOPS-enc
16k-IOPS
8k-IOPS
4k-IOPS
We have earlier this morning looped in our supplier-support and are actively working on restoring services as fast as possible, further updates will be posted here.October 14, 2025 14:41 CEST
October 14, 2025 12:41 UTC
[Identified] Partial Service Disruption
The supplier is actively analysing our problem and issue. We continue to monitor customer impact and will help where possible. We will update this information again once we have any progress or by end of business today.October 14, 2025 17:52 CEST
October 14, 2025 15:52 UTC
[Identified] Partial Service Disruption
We will now start taking corrective actions on the storage platform. More information will be posted shortly.October 14, 2025 20:57 CEST
October 14, 2025 18:57 UTC
[Identified] Partial Service Disruption
At the moment the work continues together with the storage vendor restoring the cluster in STO1. We will update as soon as we have and ETA for the recovery.October 14, 2025 22:25 CEST
October 14, 2025 20:25 UTC
[Identified] Partial Service Disruption
We are now performing more corrective actions on the storage platform, more updates to follow.October 14, 2025 22:44 CEST
October 14, 2025 20:44 UTC
[Monitoring] Degraded Performance
Late-evening update;
Core-service for managing volumes has had functionality restored and volume-management is operational again.
We are still considering this as a performance-degraded status and will continue working on investigations and monitoring this evening.October 14, 2025 23:23 CEST
October 14, 2025 21:23 UTC
[Monitoring] Degraded Performance
Evening update;
We are stepping down from active work on the service at the moment, the management-services are stable and the issues and open incidents we have seen are now resolved.
If you are still experiencing any issues with services related to utilizing V1-storage we advice to perform a application and/or instance-restart and that should resolve any remaining issues.