Scaleway Status

Investigating: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Investigating: To prevent further issue, we will have to preemptively shut down multiple services in the datacenter. You may encounter downtime on your service. 
We are doing our best to recover the situation as soon as possible.

Investigating: We are continuing to monitor for any further issues.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Due to current temperatures, a lot of our services are impacted and in degraded performance. We are currently mitigating the issue and monitoring to avoid more troubles.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Since 16:30 CEST, the error rate is under the nominal threshold, we are still monitoring closely

Monitoring: Due to current temperatures, a lot of our services are impacted and in degraded performance. We are currently mitigating the issue and monitoring to avoid more troubles.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: The switch has rebooted several times, same thing for some servers.

Identified: Our engineers noticed that the billing for our Apple Silicon products is not up to date. It will be retro-actively resumed 7/16/2025.

Investigating: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Investigating: To prevent further issue, we will have to preemptively shut down multiple services in the datacenter. You may encounter downtime on your service. 
We are doing our best to recover the situation as soon as possible.

Investigating: We are continuing to monitor for any further issues.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Due to current temperatures, a lot of our services are impacted and in degraded performance. We are currently mitigating the issue and monitoring to avoid more troubles.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Since 16:30 CEST, the error rate is under the nominal threshold, we are still monitoring closely

Monitoring: Due to current temperatures, a lot of our services are impacted and in degraded performance. We are currently mitigating the issue and monitoring to avoid more troubles.

Resolved: This incident has been resolved.

Monitoring: Between July 3rd 2:00 PM UTC and July 4th 11:00 AM UTC, customers may have experienced high latencies on Object Storage in the NL-AMS region. This was due to an internal rebuild process.

To limit the impact, operations were slowed down during the event. The situation has now stabilized and we are currently monitoring the service closely.

Investigating: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Investigating: To prevent further issue, we will have to preemptively shut down multiple services in the datacenter. You may encounter downtime on your service. 
We are doing our best to recover the situation as soon as possible.

Investigating: We are continuing to monitor for any further issues.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Due to current temperatures, a lot of our services are impacted and in degraded performance. We are currently mitigating the issue and monitoring to avoid more troubles.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Since 16:30 CEST, the error rate is under the nominal threshold, we are still monitoring closely

Monitoring: Due to current temperatures, a lot of our services are impacted and in degraded performance. We are currently mitigating the issue and monitoring to avoid more troubles.

Investigating: We are continuing to investigate this issue.

Investigating: Starting on 2024/11/14 17:47 UTC, clients might experience issues pushing/pulling images from rg.fr-par.scw.cloud due to a certificate issue.

As a result, users from Serverless Functions/Containers using an image hosted on rg.fr-par.scw.cloud might also get impacted, as their functions/containers won't be able to start. Impacts for Serverless Functions/Containers are:

• instances that cannot start (scale up might be impossible)
• requests timeouting or 5xx errors if no instances are available.

We are currently investigating this issue, and apologize for the inconvenience.

Investigating: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Investigating: To prevent further issue, we will have to preemptively shut down multiple services in the datacenter. You may encounter downtime on your service. 
We are doing our best to recover the situation as soon as possible.

Investigating: We are continuing to monitor for any further issues.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Due to current temperatures, a lot of our services are impacted and in degraded performance. We are currently mitigating the issue and monitoring to avoid more troubles.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Since 16:30 CEST, the error rate is under the nominal threshold, we are still monitoring closely

Monitoring: Due to current temperatures, a lot of our services are impacted and in degraded performance. We are currently mitigating the issue and monitoring to avoid more troubles.

Identified: - Current progress on this incident:

Most of the disk attach are fixed, we still have some timeouts remaining Detach will no longer fail on those half-attached volumes Disks which were not attached properly during the incident wont be fixed automatically, you can detach/attach them Root cause not known

• Next actions on Instance side:

We will deploy a second release this morning with an even higher timeout value We'll wait 1-2 hours to ensure everything is OK before passing the status to monitoring as we don't know the root cause

Investigating: Since Nov 6th at 10 PM (FR), some databases have failed to start, and users are unable to connect to their databases. The issue is linked to the incident detailed at https://status.scaleway.com/incidents/n7k8t96f4cjy.

Investigating: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Investigating: To prevent further issue, we will have to preemptively shut down multiple services in the datacenter. You may encounter downtime on your service. 
We are doing our best to recover the situation as soon as possible.

Investigating: We are continuing to monitor for any further issues.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Due to current temperatures, a lot of our services are impacted and in degraded performance. We are currently mitigating the issue and monitoring to avoid more troubles.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Since 16:30 CEST, the error rate is under the nominal threshold, we are still monitoring closely

Monitoring: Due to current temperatures, a lot of our services are impacted and in degraded performance. We are currently mitigating the issue and monitoring to avoid more troubles.

Identified: A small subset of customers have an interruption of logs and metrics coming from Scaleway products since the 13th of June. Custom Data Sources are not affected.

Identified: - Current progress on this incident:

Most of the disk attach are fixed, we still have some timeouts remaining Detach will no longer fail on those half-attached volumes Disks which were not attached properly during the incident wont be fixed automatically, you can detach/attach them Root cause not known

• Next actions on Instance side:

We will deploy a second release this morning with an even higher timeout value We'll wait 1-2 hours to ensure everything is OK before passing the status to monitoring as we don't know the root cause

Investigating: Since Nov 6th at 10 PM (FR), some databases have failed to start, and users are unable to connect to their databases. The issue is linked to the incident detailed at https://status.scaleway.com/incidents/n7k8t96f4cjy.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently experiencing an issue affecting the instances infrastructure across all availability zones in FR-PAR.

Impact:

• Starting and stopping instances with local storage may experience significant delays
• Snapshot tasks are currently stuck and unable to progress

Investigating: We are continuing to investigate this issue.

Investigating: We are currently experiencing an issue affecting the instances infrastructure across all availability zones in FR-PAR.

Impact:

• Starting and stopping instances with local storage may experience significant delays
• Snapshot tasks are currently stuck and unable to progress

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Since 16:30 CEST, the error rate is under the nominal threshold, we are still monitoring closely

Monitoring: Due to current temperatures, a lot of our services are impacted and in degraded performance. We are currently mitigating the issue and monitoring to avoid more troubles.

Identified: On July 15th at 15:00:00, the Mistral Small 3.1 model experienced instabilities, leading to potential disruptions in service. This issue may affect the performance and availability of the Generative APIs relying on this model.

Investigating: Since 30th June 2025, 11:30am, we are experiencing periodic instabilities on the Mistral Small 3.1 inference engine. This may result in short, intermittent service disruptions for affected users. Investigations are ongoing to find and fix the root cause.

Investigating: Since 6th July 2025, 8:45 PM, Gemma 3 is currently experimenting slow response times and Llama 3.3 experienced a few short disruptions

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: Issues on fr-par-2 impacting multiple products. Our team is actively working on it.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently experiencing an issue affecting the instances infrastructure across all availability zones in FR-PAR.

Impact:

• Starting and stopping instances with local storage may experience significant delays
• Snapshot tasks are currently stuck and unable to progress

Investigating: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Investigating: To prevent further issue, we will have to preemptively shut down multiple services in the datacenter. You may encounter downtime on your service. 
We are doing our best to recover the situation as soon as possible.

Investigating: We are continuing to monitor for any further issues.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Due to current temperatures, a lot of our services are impacted and in degraded performance. We are currently mitigating the issue and monitoring to avoid more troubles.

Resolved: This incident has been resolved.

Monitoring: Between July 3rd 2:00 PM UTC and July 4th 11:00 AM UTC, customers may have experienced high latencies on Object Storage in the NL-AMS region. This was due to an internal rebuild process.

To limit the impact, operations were slowed down during the event. The situation has now stabilized and we are currently monitoring the service closely.

Resolved: This incident has been resolved.

Monitoring: We experienced a temporary issue affecting a limited number of servers at DC2. This was due to an internal operation in the datacenter. As a result, some servers may have become unavailable during the incident.

All impacted servers are currently being restored. A full recovery is in progress.

Resolved: This incident has been resolved.

Monitoring: Switch has been replaced. Servers are back online.

We are monitoring the situation.

Investigating: We are experiencing a temporary issue affecting some dedicated server.

Team has been warned.

Resolved: This incident has been resolved.

Monitoring: The faulty switch has been powered back on. Optical modules have been replaced. The switch is now operational again.

Connectivity is being restored for the affected Dedibox servers. We continue to monitor the situation to ensure full recovery.

Identified: The issue has been identified and a fix is being implemented.

Monitoring: Physical intervention at the DC is ongoing

Investigating: We are currently experiencing a network incident in DC3 due to a switch failure. This is impacting a subset of Dedibox servers, which may face intermittent or total loss of network connectivity.

Our teams are actively working to restore full service as quickly as possible.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: The switch has rebooted several times, same thing for some servers.

Resolved: This incident has been resolved.

Monitoring: The faulty switch has been replaced. All affected servers have been back online since 09:41.

If you’re still experiencing issues, please contact our Support team.

Identified: We are currently experiencing a network incident in DC5 due to a switch failure. This is impacting a subset of Dedibox servers, which may face intermittent or total loss of network connectivity.

Our teams are actively working to restore full service as quickly as possible.

Resolved: This incident has been resolved.

Investigating: We have detected a switch down Servers in that rack currently have no public network access and are unreachable.

Issue has been forwarded to our team for resolution.

Resolved: This incident has been resolved.

Investigating: The following OS cannot be installed on Dedibox : archlinux, esxi and windows.

Investigating: The IP 51.159.208.135 is blacklisted by Microsoft.

We are currently working on it.

Resolved: This incident has been resolved.

Investigating: An unexpected server failure occurred on san-ssd-3.rpn.online.net, causing the loss of the master node in the cluster. As a result, the RPN-SAN storage service became unavailable.

Storage team is actively investigating the root cause and working to restore service as quickly as possible.

Resolved: There was an issue with the uplink. The incident has been resolved.

Investigating: The RPN switch is currently unreachable, resulting in a loss of RPN connectivity in rack H7. The public network remains operational.

Resolved: This incident has been resolved.

Monitoring: We experienced a temporary issue affecting a limited number of servers at DC2. This was due to an internal operation in the datacenter. As a result, some servers may have become unavailable during the incident.

All impacted servers are currently being restored. A full recovery is in progress.

Resolved: This incident has been resolved.

Investigating: An unexpected server failure occurred on san-ssd-3.rpn.online.net, causing the loss of the master node in the cluster. As a result, the RPN-SAN storage service became unavailable.

Storage team is actively investigating the root cause and working to restore service as quickly as possible.

Resolved: This incident has been resolved.

Monitoring: The faulty switch has been powered back on. Optical modules have been replaced. The switch is now operational again.

Connectivity is being restored for the affected Dedibox servers. We continue to monitor the situation to ensure full recovery.

Identified: The issue has been identified and a fix is being implemented.

Monitoring: Physical intervention at the DC is ongoing

Investigating: We are currently experiencing a network incident in DC3 due to a switch failure. This is impacting a subset of Dedibox servers, which may face intermittent or total loss of network connectivity.

Our teams are actively working to restore full service as quickly as possible.

Resolved: This incident has been resolved.

Investigating: We have detected a switch down Servers in that rack currently have no public network access and are unreachable.

Issue has been forwarded to our team for resolution.

Resolved: This incident has been resolved.

Monitoring: Switch has been replaced. Servers are back online.

We are monitoring the situation.

Investigating: We are experiencing a temporary issue affecting some dedicated server.

Team has been warned.

Resolved: This incident has been resolved.

Monitoring: The faulty switch has been replaced. All affected servers have been back online since 09:41.

If you’re still experiencing issues, please contact our Support team.

Identified: We are currently experiencing a network incident in DC5 due to a switch failure. This is impacting a subset of Dedibox servers, which may face intermittent or total loss of network connectivity.

Our teams are actively working to restore full service as quickly as possible.