- Level
- confirmed
- Worst impact
- Degraded
- Components
- SAN
What to do
Check whether you use Scaleway SAN. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3d 3h it lasted.
Anything that failed between 2026-03-31 13:04 UTC and 2026-04-03 16:21 UTC may need a replay.Subscribe to Scaleway's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=scaleway works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Scaleway 4
- investigating
Between 23:45 and 01:30 on sunday, 4 disks failed on our SAN Cluster server, compromising the RAID configuration. We are attempting to recover data using a spare server.
provider
- investigating
We are continuing to investigate this issue.
provider
- identified
The RAID is currently being rebuilt. An operation to recover the service is underway. The service should be back tomorrow if everything goes smoothly.
provider
- resolved
The issue has been resolved. Please contact our support team if you have any issue with our SAN.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-8f745c8dcf
Is Scaleway still down?
No, this incident was resolved 2026-04-03 16:21 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
3d 3h, from 2026-03-31 13:04 UTC to 2026-04-03 16:21 UTC, by the times Scaleway posted.
What was affected?
Scaleway named SAN.
What caused it?
Scaleway hasn't published a root cause. If it does, it shows here.
Where does this come from?
Scaleway's official status page, https://status.scaleway.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.