Scaleway: [BLOCK-STORAGE][NL-AMS-1] Multiple products impacted by a Block storage issue.
Timeline of updates
- resolved
This incident started at 22:27 UTC when latency began to rise noticeably. At 22:40 UTC, 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 UTC, The Storage team finished to reintegrate the excluded disks and the cluster returned to a healthy state. Post‑00:UTC, Product teams cleared the remaining stuck Instances and Databases. No data loss detected on the affected cluster.
From Scaleway’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.scaleway.com (opens in new tab).
Cite this
Status incident (vendor impact label: critical) posted by Scaleway, started 2026-02-27 23:18 UTC, resolved after 5.5 h, 1 update(s).
- Title
- [BLOCK-STORAGE][NL-AMS-1] Multiple products impacted by a Block storage issue.
- Vendor
- Scaleway
- Date
- URL
- https://rewindex.com/company/scaleway/incidents/m2fcjyd8kpmj
Scaleway profileRecent Scaleway incidentsAll outages on February 27, 2026Scaleway in February 2026MarkdownJSON