- Level
- confirmed
- Worst impact
- Degraded
- Components
- Dedibox, DC1, DC2, DC3, DC4, DC5
- Regions
- us
- Down Index
- 27of 100
What to do
Check whether you use Scaleway Dedibox, DC1, DC2, DC3 and 2 more in us. 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 4d 22h it lasted.
Anything that failed between 2026-08-13 16:30 UTC and 2026-08-18 15:29 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
While putting in production a new IXP, they forgot to update the ACL on their side but we were still able to reach the RS, so we announced our prefixes but the other members of the IXP weren’t able to send traffic to us, leading to blackhole of 20Gbps.
provider
- resolved
We are pleased to inform you that the issue 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-28a74df0c9
Is Scaleway still down?
No, this incident was resolved 2026-08-18 15:29 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
4d 22h, from 2026-08-13 16:30 UTC to 2026-08-18 15:29 UTC, by the times Scaleway posted.
What was affected?
Scaleway named Dedibox, DC1, DC2, DC3 and 2 more in us.
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.