There were 60 Scaleway outages since February 24, 2026 totaling 1825h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.
Some customers may experience 500 errors when trying to connect to Dedibackup in DC3.
Some customers may experience 500 errors when trying to connect to Dedibackup in fr-par-1.
This incident has been resolved.
Customers may experience a high error rate on the Container Registry API.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have detected that public switches were down in DC5 Room 1 1 Rack D39. Servers in that rack currently have no network access and are unreachable, RPN network is still reachable.
The Switch is currently down and is being replaced.
Switch has been replaced network is up for the Rack D39
An incident is currently occurring on the Windows systems : - Windows 2019 Hyper-V - Windows 2019 Standard - Windows 2019 Datacenter - Windows 2022 Standard - Windows 2022 Datacenter We are currently investigating this issue.
This incident has been resolved.
Some customers paying by card may experience a display issue where the invoice shows "unpaid" even though it has been paid. We apologize for any inconvenience this may cause.
This incident has been resolved.
During a product maintenance, we have noticed an increase of latency and errors. Our team performed a rollback and monitor the situation since then. The instability was seen during approximately two hours (12h20 to 14h UTC).
The SMTP communication with TEM is currently disrupted due to a key rotation issue. This may affect the delivery of alert emails.
This incident has been resolved.
Webmail is not accessible for hostings on pf-012.whm.fr-par.scw.cloud
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Between 23:45 and 01:30 on sunday, 4 disks failed on our SAN Cluster server, compromising the RAID configuration. We are attempting to recover data using a spare server.
We are continuing to investigate this issue.
The RAID is currently being rebuilt. An operation to recover the service is underway. The service should be back tomorrow if everything goes smoothly.
The issue has been resolved. Please contact our support team if you have any issue with our SAN.
IPV6 connectivity is currently unavailable. This may affect services relying on IPV6 addresses.
IPV6 connectivity is currently unavailable on the platform pf-012.whm.fr-par.scw.cloud. This may affect services relying on IPV6 addresses. We have identified the cause and are working on a resolution.
This incident has been resolved.
Start from 30 march 2026 at 15h53 CET, Kapsule cluster creation was not possible. The incident was resolved 30 march 2026 at 17h04.
New deployments cannot be created at this time. Starting existing deployments may also result in failure.
This incident has been resolved.
On March 26, 2026, we experienced an incident affecting Serverless Containers in the following regions: pl-waw: from approximately 11:30 CET to 11:36 CET nl-ams: from approximately 13:30 CET to 13:40 CET During these periods, a platform-level component triggered an automatic redeployment of active Serverless Containers. This action was initiated without any user intervention and was unintended. The sudden scaling activity caused temporary disruptions across the Serverless platform, including brief network connectivity issues—particularly for containers connected to VPC. Impact: - Brief service interruptions for running Serverless Containers - Transient network issues, especially for Serverless Containers configured with private networks - Increased startup latency during the redeployment window All systems are now operating normally, and no further action is required from users. We sincerely apologize for the disruption. Our team has identified the cause. No reoccurrence is expected to happen. We appreciate your understanding and patience.
We are currently experiencing a partial outage affecting the Audit Trail API in the fr-par region. This may impact your ability to access or use the Audit Trail service. Customers may see 503 responses on some requests to the audit trail API, but no events are being lost.
The issue has been mitigated, and we are investigating its root cause.
This incident has been resolved.
We have performed a server maintenance for the cPanel platform 1005. A downtime of 10 min may have occured during the maintenance.
At 02:25:50 UTC+1, an RPN switch in DC5 Room 1 Rack B15 rebooted, interrupting network traffic for servers attached to it for 10 minutes.
Customers are experiencing connectivity issues through public endpoints. The public endpoint IPs are not pointing to the new nodes.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Events in PL-WAW are not being displayed in Audit Trail since 9:53 GMT+1. Those events are not lost because we have a backup solution that stores the events in case of incidents like this. We are actively working on fixing the issue.
The incident was resolved at 11:22 a.m. CET.
At 21:01 UTC+1, a public switch in Room 103 - Rack: 9-2 rebooted, causing all servers in the affected rack to lose public connectivity until the switch came back online at 21:04.
This incident has been resolved.
Qwen-3-235B-A22-Instruct is currently experiencing increased response times. We are investigating the situation.
This incident has been resolved.
At 21h35 UTC+1, a public switch in room 1-rack b43 rebooted, causing all attached servers to lose public connectivity until the switch came back online at 21h46 UTC+1.
At 21h35 UTC+1, a public switch in room 1-rack b43 rebooted, causing all attached servers to lose public connectivity until the switch came back online at 21h46 UTC+1.
This incident has been resolved.
We are currently experiencing an issue with DNS resolution for entries related to the Private Network, which is affecting MongoDB SRV record lookups. This is preventing some customers from connecting to their MongoDB instances when using Private Network endpoints. Our engineering teams are actively investigating and working to resolve the issue as quickly as possible. We sincerely apologise for the inconvenience and will share updates as soon as more information becomes available.
This incident has been resolved.
Some querier pods are not restarting after Kubernetes upgrade, causing errors when querying Scaleway Logs Datasources. This may impact the ability to view and analyze logs.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Users are currently unable to receive login emails due to a technical issue affecting the Account API in the fr-par-1 region.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Pingoru polls Scaleway's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required