- Level
- confirmed
- Worst impact
- Degraded
- Components
- nl-ams-1, nl-ams-2, nl-ams-3, Object Storage
- Down Index
- 24of 100
What to do
Check whether you use Scaleway nl-ams-1, nl-ams-2, nl-ams-3, Object Storage. 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 18d 4h it lasted.
Anything that failed between 2026-05-11 11:45 UTC and 2026-05-29 16:12 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 3
- investigating
Due to 2 servers of the same Object Storage cluster being down in 2 different AZ, access to data stored on that cluster can return 500 errors. Our team is on it.
provider
- monitoring
The issue on the second server have been fixed. The major impact started from 10h37 UTC to 11h53 UTC with roughly 1% of AMS requests resulting in errors. The team is now monitoring the situation.
provider
- resolved
This incident has been resolved.
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-8c2f959661
Is Scaleway still down?
No, this incident was resolved 2026-05-29 16:12 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
18d 4h, from 2026-05-11 11:45 UTC to 2026-05-29 16:12 UTC, by the times Scaleway posted.
What was affected?
Scaleway named nl-ams-1, nl-ams-2, nl-ams-3, Object Storage.
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.