- Level
- confirmed
- Worst impact
- Degraded
- Components
- pl-waw-1, pl-waw-2, pl-waw-3, Object Storage
- Down Index
- 24of 100
What to do
Check whether you use Scaleway pl-waw-1, pl-waw-2, pl-waw-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 1d 22h it lasted.
Anything that failed between 2026-09-28 08:49 UTC and 2026-09-30 07:22 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
Since the 25/09 (last friday), the S3 pl-waw region is overloaded with operations. We're currently working to mitigate that.
provider
- monitoring
The issue has been identified, fixes have been deployed, we're back to the nominal state, monitoring.
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-bcd0616d2d
Is Scaleway still down?
No, this incident was resolved 2026-09-30 07:22 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
1d 22h, from 2026-09-28 08:49 UTC to 2026-09-30 07:22 UTC, by the times Scaleway posted.
What was affected?
Scaleway named pl-waw-1, pl-waw-2, pl-waw-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.