Status impact color legend
- Black impact: None
- Yellow impact: Minor
- Red impact: Major
- Blue impact: Maintenance
[Serverless Functions] - [pl-waw/nl-ams] - mandatory operation to release VPC routing
Scheduled for Apr 28, 10:00 CEST - Apr 29, 04:00 CEST
Subscribe to Updates
Scheduled
From April 28st to April 29th (between 8 AM and 5 PM UTC), we will perform a mandatory operation in the pl-waw and nl-ams regions to release VPC routing.
Over the course of these two days, changes will be applied to all Serverless Functions namespaces in the pl-waw and nl-ams regions.
While this operation is seamless most of the time, users may observe the following behaviors:
- Namespaces will pass temporarily in "unknown" status. This may take up to 15 minutes, depending on the number of resources inside the namespace.
- Function instances will be created. This is mandatory to ensure the functions are working properly. If a function 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 function running, even if it's configured with max_scale = 1, and even if there is no incoming traffic. The function will downscale as soon as the operation is over.
- Long running requests made during this operation may fail, as we roll out function 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 functions cannot start because of an applicative error, the functions will always be reachable.
Thank you for your understanding, and we apologize for any inconvenience this may cause.
Over the course of these two days, changes will be applied to all Serverless Functions namespaces in the pl-waw and nl-ams regions.
While this operation is seamless most of the time, users may observe the following behaviors:
- Namespaces will pass temporarily in "unknown" status. This may take up to 15 minutes, depending on the number of resources inside the namespace.
- Function instances will be created. This is mandatory to ensure the functions are working properly. If a function 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 function running, even if it's configured with max_scale = 1, and even if there is no incoming traffic. The function will downscale as soon as the operation is over.
- Long running requests made during this operation may fail, as we roll out function 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 functions cannot start because of an applicative error, the functions will always be reachable.
Thank you for your understanding, and we apologize for any inconvenience this may cause.