Status impact color legend
- Black impact: None
- Yellow impact: Minor
- Red impact: Major
- Blue impact: Maintenance
[BLOCK-STORAGE][NL-AMS-1] Multiple products impacted by a Block storage issue.
Incident
Report for Scaleway
Resolved
This incident started at 22:27 CET when latency began to rise noticeably.
At 22:40 CET, A control‑plane fault caused several disks to be excluded at once from the cluster. The resulting load on the control plane then prevented the cluster from self‑recovering, progressively freezing read/write for a maximum of 31 % of this cluster.
At 00:25 CET, The Storage team finished to reintegrate the excluded disks and the cluster returned to a healthy state.
Post‑00:25 CET, Product teams cleared the remaining stuck Instances and Databases.
No data loss detected on the affected cluster.
At 22:40 CET, A control‑plane fault caused several disks to be excluded at once from the cluster. The resulting load on the control plane then prevented the cluster from self‑recovering, progressively freezing read/write for a maximum of 31 % of this cluster.
At 00:25 CET, The Storage team finished to reintegrate the excluded disks and the cluster returned to a healthy state.
Post‑00:25 CET, Product teams cleared the remaining stuck Instances and Databases.
No data loss detected on the affected cluster.
Update
We are working on managing some side effects.
The situation is still stable at the moment.
The situation is still stable at the moment.
Monitoring
Latencies should be back to normal.
We continue to monitor the situation.
We continue to monitor the situation.
Update
The situation has been stabilized.
Some latencies may still be observed; we continue to monitor the situation.
We keep providing updates and will notify you once everything is fully back to normal.
Some latencies may still be observed; we continue to monitor the situation.
We keep providing updates and will notify you once everything is fully back to normal.
Update
We are still working to stabilize the situation.
Thank you again for your patience and understanding.
Thank you again for your patience and understanding.
Identified
The situation is now stabilizing.
Update
Our team remains fully engaged in resolving the problem.
We truly appreciate your patience and understanding.
We truly appreciate your patience and understanding.
Update
Our team is still actively working on the issue.
Thank you again for your patience and understanding.
Thank you again for your patience and understanding.
Update
Our team is still actively working on the issue.
We will continue to provide updates every 30 minutes
Thank you for your patience and understanding.
We will continue to provide updates every 30 minutes
Thank you for your patience and understanding.
Investigating
A block storage cluster on nl-ams-1 is having difficulties impacting multiple products. Our teams are on it.
This incident affected: Elements - Products (Instances, Block Storage, Kubernetes Kapsule, Databases) and Elements - AZ (nl-ams-1).