[Kapsule] - [All - region] - infrastructure migration
On Wednesday 4th to Friday 6th of November, from 8:00 AM CET to 7:00 PM CET, we will perform a mandatory upgrade on our infrastructure. This upgrade aims to enhance internal resiliency. This migration will cause apiserver restart one or more time. We will keep you updated, and will inform you when the upgrade is finished. We sincerely apologize for any inconvenience.
The latest update from Scaleway.
State
Scheduled
Starts
in 4 d
2026-11-06 07:00 UTC
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Scaleway
On Wednesday 4th to Friday 6th of November, from 8:00 AM CET to 7:00 PM CET, we will perform a mandatory upgrade on our infrastructure. This upgrade aims to enhance internal resiliency. This migration will cause apiserver restart one or more time. We will keep you updated, and will inform you when the upgrade is finished. We sincerely apologize for any inconvenience.
Affected components
26Scaleway in the last 90 days
Full historyIncidents in 90 days
54
Days with an incident
28
Median duration
15 h 5 min
This incident
Not comparable
Other Scaleway incidents
All incidentsScaleway·[BILLING] - Billing consumptions in November are not up-to-date
Scaleway reports that November consumption data is not up to date in the Billing console and the billing APIs. The affected components are Billing and Elements - Products - Billing. Scaleway is investigating the issue.
Scaleway·[NETWORK] - [DC5] RPN switch is down on DC5/S9/C52
The RPN switch on DC5/S9/C52 is down. The RPN service and Dedibox in the DC5 region do not work. Scaleway reports that the incident is resolved. It lasted 2 hours and 36 minutes.
Scaleway·[Generative APIs] Model mistral-small-3.2-24b-instruct-2506 unavailable.
01/11/2026 - 21:00 UTC+1 - Service started to be degradated 02/11/2026 - 2:00 UTC+1 - Service was unavailable 02/11/2026 - 9:00 UTC+1 - A fix has been implemented, service is available
Scaleway·[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
Scaleway Serverless SQL DB backups did not run in the fr-par region. The components Serverless-Database and Elements - Products - Serverless-Database had degraded performance. Scaleway reports that the incident is resolved, and it lasted 3 days and 4 hours.
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.cc/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.cc/feed.xml?providers=scaleway/feed subscribe https://outages.cc/feed.xml?providers=scalewayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane