Skip to content
OutageDeck

Incident detail

[CAAS] - [fr-par] - namespaces and containers stuck in transient statuses

Resolved incidentMinor

Timeline window

to

Outage alerts

Get alerted the next time Scaleway breaks

Free email alerts for up to 5 providers — no card, live in about a minute. Paid plans add Slack, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Scaleway alerts work

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. 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.

  2. 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.