Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Outage in Scaleway

[Serverless Containers] - [fr-par] - mandatory operation to prepare for new v1 API (1/2)

Resolved Minor
March 24, 2026 - Started about 1 month ago - Lasted 29 minutes
Official incident page

Incident Report

Summary AI Generated

Scaleway performed a mandatory maintenance operation on Serverless Containers in the fr-par region to prepare for their new v1 API upgrade. During the operation, users experienced temporary namespace upgrades (blocking write operations for up to 15 minutes), multiple container instances running simultaneously, potential failures of long-running requests, and cron jobs triggering multiple times. The maintenance was completed successfully, with containers remaining reachable throughout the process except for application-level errors.

On April 1st (between 8 AM and 5 PM UTC), we will perform a mandatory operation in the fr-par region to prepare for the upcoming v1 API (coming soon). This operation will be carried out in two maintenance windows: - April 1, 2026 - April 8–9, 2026 Over the course of these three days, changes will be applied to all Serverless Containers namespaces in the fr-par region. While this operation is seamless most of the time, users may observe the following behaviors: - Namespaces will pass temporarily in "upgrading" status. This may take up to 15 minutes, depending on the number of resources inside the namespace. During this time, all write operations on the namespace (update namespace, create container, update container, delete container, etc.) will be impossible. Read operations will work as usual. - Container instances will be created. This is mandatory to ensure the containers are working properly. If a container fails to start, the "status" field will change to "error", and the "error_message" field will show the error, so users can fix it. During that process, users could see multiple instances of their container running, even if it's configured with max_scale = 1, and even if there is no incoming traffic. The Container will downscale as soon as the operation is over. - Long running requests made during this operation may fail, as we roll out Container instances. - Crons might be triggered multiple times during the operation. Crons with frequent schedules (such as every minute) might be more impacted. Please note that during this process, unless the containers cannot start because of an applicative error, the containers will always be reachable. This process is mandatory to prepare a seamless upgrade to the new v1 API, which will bring enhanced features and improvements. More details here: https://www.scaleway.com/en/docs/serverless-containers/reference-content/v1-migration-guide/ Thank you for your understanding, and we apologize for any inconvenience this may cause.
Components affected
Scaleway fr-par-1

Trusted by 1,000+ teams

Never miss outages in third-party dependencies

Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.

IsDown status aggregator dashboard
Latest Updates ( sorted recent to last )
INVESTIGATING about 1 month ago - at 03/24/2026 09:17AM

On April 1st (between 8 AM and 5 PM UTC), we will perform a mandatory operation in the fr-par region to prepare for the upcoming v1 API (coming soon).

This operation will be carried out in two maintenance windows:
- April 1, 2026
- April 8–9, 2026

Over the course of these three days, changes will be applied to all Serverless Containers namespaces in the fr-par region.

While this operation is seamless most of the time, users may observe the following behaviors:

- Namespaces will pass temporarily in "upgrading" status. This may take up to 15 minutes, depending on the number of resources inside the namespace. During this time, all write operations on the namespace (update namespace, create container, update container, delete container, etc.) will be impossible. Read operations will work as usual.
- Container instances will be created. This is mandatory to ensure the containers are working properly. If a container fails to start, the "status" field will change to "error", and the "error_message" field will show the error, so users can fix it. During that process, users could see multiple instances of their container running, even if it's configured with max_scale = 1, and even if there is no incoming traffic. The Container will downscale as soon as the operation is over.
- Long running requests made during this operation may fail, as we roll out Container instances.
- Crons might be triggered multiple times during the operation. Crons with frequent schedules (such as every minute) might be more impacted.

Please note that during this process, unless the containers cannot start because of an applicative error, the containers will always be reachable.

This process is mandatory to prepare a seamless upgrade to the new v1 API, which will bring enhanced features and improvements. More details here: https://www.scaleway.com/en/docs/serverless-containers/reference-content/v1-migration-guide/

Thank you for your understanding, and we apologize for any inconvenience this may cause.

Never miss outages in third-party dependencies

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 6320 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook