- Level
- confirmed
- Worst impact
- Degraded
- Components
- fr-par-1, fr-par-2, fr-par-3, Serverless Container
- Down Index
- 24of 100
What to do
Check whether you use Scaleway fr-par-1, fr-par-2, fr-par-3, Serverless Container. 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 20h 45m it lasted.
Anything that failed between 2026-08-17 16:41 UTC and 2026-08-18 13:26 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
On a small subset of our fr-par infrastructure, between 2026-08-17 09:20 UTC and 2026-08-17 16:15 UTC, some containers attached to a Private Network were not able to reach resources inside that PN. This issue is likely due to a faulty deployment, that we have reverted at 2026-08-17 16:15 UTC. Containers should now be able to reach resources in their Private Network as before. If your container has faced issues like "timeouts" or "connection error" while trying to reach a resource through their private endpoint during the time range above, the issues are likely linked. If you still continue to face these errors, feel free to open a support ticket. We sincerely apologize for any inconvenience.
provider
- monitoring
We have finished rolling back the faulty deployment. Situation should be good now for all users.
provider
- resolved
After investigation, we have found the root cause. The issue happened because of blackholed traffic, but only on some Private Networks with a specific configuration: - PNs with ACLs - PNs inside VPCs with "enable_routing" set to false Anyway, we have rolled back the component causing the issues, so this error shouldn't happen anymore. Sorry again for any inconvenience.
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-e70ed425a4
Is Scaleway still down?
No, this incident was resolved 2026-08-18 13:26 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
20h 45m, from 2026-08-17 16:41 UTC to 2026-08-18 13:26 UTC, by the times Scaleway posted.
What was affected?
Scaleway named fr-par-1, fr-par-2, fr-par-3, Serverless Container.
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.