Provider
ScalewayIncident detail
[CAAS] - [fr-par] - namespaces and containers stuck in transient statuses
Timeline window
to
Get alerted the next time Scaleway breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
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.
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.
Keep exploring
More from Scaleway
Neighboring incidents on Scaleway's timeline and the rest of their record on OutageDeck.
← Older incident
[KUBERNETES] - [fr-par] - Product API down
Newer incident →
[JOBS] - [fr-par] - Execution of some job runs was interrupted
- [Generative API] - [global] - Deepseek v4.1 flash timeoutsMinor · Active
- [Serverless-Database]- [fr-par] - slow cold start for the DB and DB in status errorMinor
- [Dedibox] - PARDC3 / Room 4-4 / Rack C18 - PUB switch unreachableMinor · Active
- [Instances] - AMS1 / Room Hall6 / Rack 6.12.32 - ams1dc1-net-f02lf75.ams1 crashes multiple timeMinor