- Level
- confirmed
- Worst impact
- Degraded
- Components
- fr-par-1, fr-par-2, fr-par-3, Container Registry
- Down Index
- 9of 100
What to do
Check whether you use Scaleway fr-par-1, fr-par-2, fr-par-3, Container Registry. 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-11-01 21:17 UTC and 2026-11-01 21:17 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
Between 8:00 PM and 9:30 PM, requests to the Container Registry API in the FR-PAR region returned the following error: “Upstream request timeout.”
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-08f7265e4f
Is Scaleway still down?
No, this incident was resolved 2026-11-01 21:17 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
0m, from 2026-11-01 21:17 UTC to 2026-11-01 21:17 UTC, by the times Scaleway posted.
What was affected?
Scaleway named fr-par-1, fr-par-2, fr-par-3, Container Registry.
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.