- Level
- confirmed
- Worst impact
- Degraded
- Components
- pl-waw-1, pl-waw-2, pl-waw-3, IAM
- Down Index
- 17of 100
What to do
Check whether you use Scaleway pl-waw-1, pl-waw-2, pl-waw-3, IAM. 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 38m it lasted.
Anything that failed between 2026-03-25 09:56 UTC and 2026-03-25 10:34 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 2
- investigating
Events in PL-WAW are not being displayed in Audit Trail since 9:53 GMT+1. Those events are not lost because we have a backup solution that stores the events in case of incidents like this. We are actively working on fixing the issue.
provider
- resolved
The incident was resolved at 11:22 a.m. CET.
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-e0536ca60e
Is Scaleway still down?
No, this incident was resolved 2026-03-25 10:34 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
38m, from 2026-03-25 09:56 UTC to 2026-03-25 10:34 UTC, by the times Scaleway posted.
What was affected?
Scaleway named pl-waw-1, pl-waw-2, pl-waw-3, IAM.
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.