Scaleway
Scaleway is reporting degraded
Partially Degraded Service
P2 - [WEBHOSTING] - PHP Emergency maintenance
Scaleway reports that PHP hosting services do not work on Classic shared hosting. PHP 4 websites stay in maintenance and show a maintenance page. Scaleway has identified the problem and deployed patched PHP versions 5.6 to 7.3. Customers can move a PHP 4 website to PHP 5.6 or later to bring it back online.
[fr-par] [Serverless SQL DB] Backups will be suspended on Friday and Saturday nights
Scaleway Serverless SQL DB backups do not run in the fr-par region. The impact is degraded on Serverless-Database components. Scaleway identified the cause and suspended backups on Friday and Saturday nights. Backups start again on Monday morning.
[fr-par-1] Latencies spikes during the day following capacity increase in one of block storage cluster
Scaleway Block Storage has latency spikes in the fr-par-1 region. This degrades Block Storage, Databases, and Instances. Scaleway identified the problem and applies a fix rack by rack. Data must be removed first, so migrations run slowly and continue through the weekend.
[GenerativeAPI] - Deepseek-v4/v4.1-flash timeouts
Scaleway reports that some requests to the deepseek-v4-flash and deepseek-v4.1-flash models on the Generative API had elevated timeouts. The error rates are improving and Scaleway monitors the situation.
[Support] Delays in ticket processing
Scaleway reports delays in ticket processing for the Excellence and Miscellaneous - Excellence components. Scaleway identified the problem and states that ticket processing takes longer than usual. The incident started on 26 October 2026 and is not resolved.
[Support] Call Handling Delays
Scaleway reports telephone call handling delays. The affected components are Excellence and Miscellaneous - Excellence. Scaleway has identified the problem and states that a high volume of requests causes the delays. Scaleway asks customers to submit a ticket instead of a phone call.
[Generative API] - [global] - GLM-5.3 timeouts
GLM-5.3 requests on the Scaleway Generative API time out. The problem affects all regions in France, the Netherlands, Poland, and Italy, including Elements AZ components. Scaleway reports that it put a fix in place and now monitors the result.
Degraded Performances on it-mil APIs
Scaleway reports degraded performance on the it-mil APIs in the it-mil-1, it-mil-2, and it-mil-3 zones. Scaleway implemented a fix and now monitors the results. The incident stays open.
History
Incidents in 90 days
50
Days with an incident
27
Median duration
17 h 50 min
Longest incident
18 days
Components
74Dedibox - Products
Elements - Products
Oct 29, 2026
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.status.scaleway.com
This incident has been resolved.status.scaleway.com
The IP address 51.159.124.109 has been blacklisted by Spamhaus. It is possible that some emails may still be rejected if this listing is cached. The incident for this IP address lasted from: Date Listed: October 28, 2026, 6:46:49 PM Date Removed: October 28, 2026, 8:54:39 PMstatus.scaleway.com
Oct 27, 2026
This incident has been resolved.status.scaleway.com
This incident has been resolved.status.scaleway.com
This incident has been resolved.status.scaleway.com
Oct 26, 2026
This incident has been resolved.status.scaleway.com
Some requests to the deepseek-v4.1-flash model had experienced elevated timeouts. The situation has been resolved.status.scaleway.com
Oct 23, 2026
This incident has been resolved.status.scaleway.com
This incident has been resolved.status.scaleway.com
Oct 22, 2026
This incident has been resolved.status.scaleway.com
This incident has been resolved.status.scaleway.com
Oct 21, 2026
This incident has been resolved.status.scaleway.com
The Dedibox Console and API are now back online and fully operational. The security patches have been successfully applied to mitigate the PHP2Shell vulnerability. Thank you for your patience and understanding.status.scaleway.com
This incident has been resolved.status.scaleway.com
An upgrade operation of the Block storage api on fr-par-2 generated a blocking transaction which impacted the control plane of this AZ The issue occurred from 12:23 to 12:28 UTC and generated a high rate of 500 errors. The problem was quickly fixed by the engineers of the product team.status.scaleway.com
This incident has been resolved.status.scaleway.com
* 2026-10-20 17:45 CEST : Partial unavailability of custom logs datasource * 2026-10-20 18:00 CEST : mitigation deployed, stabilizing availability progressively * 2026-10-21 05:00 CEST : automated event happened, which triggered partial unavailability again for part of our customers. * 2026-10-21 09:45 CEST : stabilization of our infrastructure, back to nominal situationstatus.scaleway.com
Oct 20, 2026
Users signing in with SAML who had not yet configured MFA were unable to log in. The issue was caused by a recent frontend release. A fix has been implemented, and an updated version of the account app is being deployed.status.scaleway.com
This incident has been resolved.status.scaleway.com
This incident has been resolved.status.scaleway.com
This incident has been resolved.status.scaleway.com
Oct 19, 2026
This incident has been resolved.status.scaleway.com
This incident has been resolved.status.scaleway.com
This incident has been resolved.status.scaleway.com
This incident has been resolved.status.scaleway.com
Oct 16, 2026
This incident has been resolved.status.scaleway.com
The incident is now resolved. Customers should not see timeouts anymore. We continue to monitor the related deployments.status.scaleway.com
Oct 15, 2026
This incident has been resolved.status.scaleway.com
1st network device replaced at : 10:38 2nd network device replaced at : 11:58 Issue was due to network device that broke due to a powersurge in the rackstatus.scaleway.com
Maintenance
[Serverless Functions/Containers] - [fr-par] - infrastructure upgrade
On 11/09, from 9:00 AM UTC, we will perform a mandatory upgrade on our fr-par 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
[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
[Elastic Metal][PAR-2] Scheduled Maintenance - Infrastructure Modernization — EM-I215E-NVME Servers
A technical modernization process is currently underway on selected infrastructure in the PAR2 availability zone. - Impacted servers: EM-I215E-NVME dedicated servers with tag 'migration_required'. - Action Required: Impacted customers have received a dedicated email to perform a complimentary migration to a new server before November 4, 2026. - Unmigrated servers will be proactively powered off on November 4, 2026, to allow completion of the maintenance work. Our support team remains at your disposal to assist you throughout this migration process.
[Serverless Functions/Containers] - [pl-waw] - infrastructure upgrade
On 11/03, from 9:00 AM UTC, we will perform a mandatory upgrade on our pl-waw 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
[DEDIRACK][DC1] Changes to access control during building works
Scheduled maintenance is still in progress. Work is scheduled to be completed on the date indicated (15/11)
Affected components
10- DC1Dedibox - DatacentersMaintenance
- HostingDedibox - ProductsMaintenance
- APIsElements - ProductsDegraded
- ExcellenceMiscellaneousDegraded
- DedirackDedibox - ProductsMaintenance
- Block StorageElements - ProductsDegraded
- DatabasesElements - ProductsDegraded
- Elastic MetalElements - ProductsDegraded
- InstancesElements - ProductsDegraded
- Serverless-DatabaseElements - ProductsDegraded
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=scalewayGo from tracking outages to fixing production issues with Polylane.
Try Polylane