[Serverless Functions/Containers] - [nl-ams] - infrastructure upgrade
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 mi
The latest update from Scaleway.
State
Scheduled
Starts
in 3 d
2026-11-05 08:00 UTC
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Scaleway
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 mi
Affected components
10Scaleway in the last 90 days
Full historyIncidents in 90 days
51
Days with an incident
28
Median duration
16 h 45 min
This incident
Not comparable
Other Scaleway incidents
All incidentsScaleway·[Container Registry] FR-PAR API unreacheable upstream request timeout.
Between 8:00 PM and 9:30 PM, requests to the Container Registry API in the FR-PAR region returned the following error: “Upstream request timeout.”
Scaleway·[fr-par] [Serverless SQL DB] Backups will be suspended on Friday and Saturday nights
Backups do not run for Serverless SQL DB in the fr-par region on Friday nights and Saturday nights. Scaleway reports the cause as identified. Backup runs start again on Monday morning.
Scaleway·[NL-AMS] - 20% of client requests failed with HTTP 503 errors
October 28, 2026 – 16:14 to 16:27 UTC Approximately 20% of Serverless Containers requests in nl-ams returned HTTP 503 errors, and some active client connections may have been interrupted.
Scaleway·[fr-par-1] Latencies spikes during the day following capacity increase in one of block storage cluster
Scaleway reports latency spikes on Block Storage, Databases, and Instances in the fr-par-1 region. Scaleway identified the problem and applies a fix rack by rack. Data moves slowly to limit more latency, and the work continues through the weekend.
Scaleway·[fr-par] [Serverless SQL DB] All SQL databases are unavailable
This incident has been resolved.
Follow Scaleway
Your coding agent knows when Scaleway is down, and tells you when a failure is theirs, not yours. You can also get Scaleway incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "scaleway" and tell me if Scaleway has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=scaleway/feed subscribe https://outages.live/feed.xml?providers=scalewayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane