- Level
- confirmed
- Worst impact
- Degraded
- Components
- Instances, VPC
- Down Index
- 9of 100
What to do
Check whether you use Scaleway Instances, VPC. 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 0m it lasted.
Anything that failed between 2026-08-17 14:08 UTC and 2026-08-17 14:08 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 1
- resolved
Customers may have experienced connectivity issues affecting some instances in the PL-WAW-2 region, preventing access via VPC. The issue was caused by a misconfiguration applied to an internal component. A fix was applied, and connectivity has been restored.
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-c207417a86
Is Scaleway still down?
No, this incident was resolved 2026-08-17 14:08 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
0m, from 2026-08-17 14:08 UTC to 2026-08-17 14:08 UTC, by the times Scaleway posted.
What was affected?
Scaleway named Instances, VPC.
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.