- Level
- confirmed
- Worst impact
- Degraded
- Components
- Serverless Container
- Down Index
- 15of 100
What to do
Check whether you use Scaleway 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 22m it lasted.
Anything that failed between 2026-07-22 09:33 UTC and 2026-07-22 09:55 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
- identified
Following incident on Compute instances (https://status.scaleway.com/incidents/bsp2y5fysy9w), a few Serverless Containers and namespaces on fr-par region have been stuck in transient statuses (updating/deleting) during the night. Not all resources were impacted, only a fraction on one part of our infrastructure (~1/10). On this part, impacted resources were either: - updated between 2026-07-21 21:07 UTC and 2026-07-21 22:05 UTC - or deleted between 2026-07-21 21:33 UTC and 2026-07-22 03:18 UTC We have fixed the statuses, so resources are not stuck anymore. But, this would require impacted users to update or delete again their namespaces/containers if the status is in error with one of these error messages: - For previously "updating" containers: Last container update could not be processed successfully. Please try again - For previously "deleting" containers: Container could not be succesfully deleted. Please try again - For previously "updating" namespaces: Last namespace update could not be processed successfully. Please try again - For previously "deleting" namespaces: Namespace could not be succesfully deleted. Please try again Sorry about any inconvenience.
provider
- resolved
Incident is now resolved. Please read instructions in the previous message if your container or namespace has one of the following error messages. 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-9b096a37a2
Is Scaleway still down?
No, this incident was resolved 2026-07-22 09:55 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
22m, from 2026-07-22 09:33 UTC to 2026-07-22 09:55 UTC, by the times Scaleway posted.
What was affected?
Scaleway named 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.