Scaleway had 302 outages in the last 2 years totaling 844h 30m of downtime — averaging 12 incidents per month.
There were 302 Scaleway outages since July 16, 2025 totaling 844h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.
The IP address 51.159.124.109 has been blacklisted by Spamhaus.
The incident has been resolved and the IP is no longer blacklisted.
Account API is down. Console may be unusable
We are continuing to investigate this issue.
Services have recovered, we are investigating, but there should not be any user facing impacts anymore.
This incident has been resolved.
[03:00]: Following the temporal migration of yesterday, the daily backups of Serverless SQL DB didn't work last night. Backups are expected to become available again later today.
Backup services have been restored and are now available.
Instabilities when contacting Scaleway APIs
A network offload of traffic caused some transient issues, the offload was stopped in order to recover all services.
The rpn device inside the rack 6.12.71 in Amsterdam is currently unreachable. For now, we don't know the root cause.
We are continuing to investigate this issue.
This incident has been resolved.
Since the 25/09 (last friday), the S3 pl-waw region is overloaded with operations. We're currently working to mitigate that.
The issue has been identified, fixes have been deployed, we're back to the nominal state, monitoring.
This incident has been resolved.
Edge Services may return truncated HTTP content due to a faulty cache server. The incident is mitigated.
This incident has been resolved.
The latest version of rescue operator was not deployed to the nl-ams and fr-par regions following the latest changes to the already-deployed Provisioner. This caused installation issues for both Linux and ESXi operating systems.
[10:34] During 3 minutes requests sent to the gpt-oss-120b could not be processed leading to 502 HTTP errors responses [10:37] Service back to normal. gpt-oss-120b able to process requests
We have detected a switch down in DC2/S301/D13 Servers in that rack has lost private network access. =================== 2026/09/20 12:37 UTC The issue has been resolved.
We are currently investigating on an issue on the webmail interface.
This incident has been resolved.
A hardware issue impacted a RPN node (dc2-7) from 17/09/26 12h11 UTC to 18/09/26 13h01. The service is now up for the clients using this node We are monitoring closely for any new issues on the node and may need another downtime if the hardware issue persist.
This incident has been resolved.
From ~9:30 to ~9:45, some of our components were not able to start after ingesting some data. A small portion of customers may have missing data in this time range
VMs with new subnet may have had issues with dns resolutions
We are currently investigating a network issue affecting instances with an IP address in the 78.232.0.0/21 range. Outbound traffic from these instances may fail to reach a significant part of the internet. Our teams are actively working on it and we will provide an update as soon as we have more information. The incident began yesterday at 5:00 p.m. UTC+1
The issue should be resolved in most destinations, our team is taking the necessary steps to ensure it works everywhere.
The issue has been resolved. If you are still experiencing issues, we invite you to create a support ticket.
[17:20] A network issue causes an internal component to be unreachable, preventing the dedicated deployment to start properly.
This incident has been resolved.
The RPN switch is unreachable, servers in this rack lost their RPN connectivity: sd-186972 to sd-186925
This incident has been resolved.
All operations are impacted. Kafka already deployed is reachable.
Retrofit mil: image were not pushed and pulled correctly, leading to api-server unavailability.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Customer websites are slow on pf-014.whm.fr-par.scw.cloud due to an overload of the server.
This incident has been resolved.
Due to an issue with our phone system, only ticket and live chat assistance are currently available. We are currently investigating the situation and will update this status as soon as we have more information.
We are continuing to investigate this issue.
The platform is accessible again. Teams are in the process of verifying that the operation of the platform is compliant. We apologize for this interruption.
Public Gateway creation/update in fr-par-1 were stuck in a transient state.
At 3:45 am. CEST on 11/09/2026, the public switch located in DC2, room S103, rack A7, has rebooted. All servers attached to it have lost public connectivity for around 10 minutes.
This incident has been resolved.
[09/09 - 16:50] The Gemma 4 models started to show un usual latencies resulting in requests timeout [10/09 - 9:00] The incident has been mitigated and response times are back to normal
This incident has been resolved.
At 10:10 AM CEST the 11/9/2026, public switch located in DC3 room S45 rack C5 has rebooted. All servers in this racks have lost public connectivity during approximately 10 minutes.
We are continuing to investigate this issue.
This incident has been resolved.