- Level
- confirmed
- Worst impact
- Degraded
- Components
- fr-par-1, fr-par-2, fr-par-3, Serverless Container
- Down Index
- 22of 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 4h 10m it lasted.
Anything that failed between 2026-11-03 10:03 UTC and 2026-11-03 14:13 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
We are investigating reports that some serverless containers in the fr-par region may be unreachable. The issue appears to be caused by a load balancer being down, affecting a subset of the serverless containers on fr-par.
provider
- monitoring
The issue was identified on LB's side; the problem is now resolved. We're monitoring for the time being but don't expect any reoccurrence.
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-564c295f41
Is Scaleway still down?
No, this incident was resolved 2026-11-03 14:13 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
4h 10m, from 2026-11-03 10:03 UTC to 2026-11-03 14:13 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.