Companies/Scaleway/Incidents

Scaleway: [Scheduled] [Serverless Containers] - [nl-ams] - mandatory operation to prepare for new v1 API

Timeline of updates

1. resolved2026-03-03 16:00 UTC

   The maintenance is finally done. A few containers that were in "error" status before the operation might now be unreachable. This is because the latest deployed container revision wasn't working, and redeploying it failed. Users with such containers (error message starts with Container is unable to start) must redeploy a working version, or configure the probes so that container instances can start in due time. Some other containers might now be in "error" status if the image has been deleted from the registry. These containers are not reachable anymore. Users with such containers (error message is image was not found in container registry) have to redeploy the container with an existing image. Finally, on v1 containers, since probes (health checks) now can restart the container if it's not starting in due time, users have to configure the probes accordingly. This is a new feature, but a breaking change from v1beta1, so we will add it in the documentation here: https://www.scaleway.com/en/docs/serverless-containers/reference-content/v1-migration-guide/#breaking-changes (opens in new tab). Sorry about any inconvenience. We invite users facing other kind of issues to reach us through a support ticket that will be prioritized. Thanks for your understanding.

From Scaleway’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Impact, status and times are the vendor’s own, as last archived. View on status.scaleway.com (opens in new tab).

Scaleway profileRecent Scaleway incidentsAll outages on March 2, 2026Scaleway in March 2026MarkdownJSON