[Serverless Functions/Containers] - [nl-ams] - infrastructure upgrade
Resolved
Updates
Resolved
Maintenance has been stopped, due to issues encountered while we were rolling out changes. More details in the dedicated incident summary: https://status.scaleway.com/incidents/kpdnmppv771c. We will resume the infrastructure upgrade process later, and will create a separate scheduled maintenance for it. We apologize for any inconvenience.
In progress
Maintenance did not go as planned and lead to connectivity issues. Refer to this dedicated status for more information: https://status.scaleway.com/incidents/kpdnmppv771c
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Scheduled
Maintenance will begin as scheduled in 60 minutes.
Scheduled
On 11/05, from 9:00 AM UTC, we will perform a mandatory upgrade on our nl-ams infrastructure. This upgrade aims to fix a few issues, most notably a bug preventing functions/containers instances to downscale properly to zero even if no traffic is received. This will also include changes allowing us to improve overall performance, and prepare for the next features. While we tried our best to reduce impacts to users, some of them are inevitable. While we rollout the upgrade, expected impacts are: - Users' running functions/containers instances will restart, several times. As a result, requests could be buffered while new instances are started, causing "cold starts", even for functions/containers with min_scale set to 1. Functions/containers with no running instances won't be impacted. - 5xx errors while calling functions/containers. As we restart system components to perform the upgrade, some in-flight requests (especially long-running ones) might be terminated before completion. Users might also notice flakiness (slow requests, timeouts), but client retries should be able to succeed. We will keep you updated, and will inform you when the upgrade is finished. We sincerely apologize for any inconvenience.