Scaleway Status

Investigating: Customers are experiencing an error 500 when attempting to install an OS on ELMA for EM-A610R-NVME, preventing the installation process from completing.

Resolved: Here is the list of affected racks in DC5 ROOM 7 : S7 D1 S7 D7 S7 D13 S7 D16 S7 D20 S7 D72 S7 C18 S7 C24 S7 C25 S7 C31

Monitoring: We experienced a network issue in a pod in DC5 for Elastic Metal, resulting in a brief disconnection. The issue has now been resolved.

Monitoring: Due to a hardware issue, some Elastic Metal instances experienced brief connectivity interruptions as BGP sessions between network devices were temporarily affected.

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

Investigating: We are experiencing some difficulties with DNS resolution via a private network. This only affects SRV records.

We are doing everything we can to resolve this quickly.

Resolved: This incident has been resolved.

Investigating: Some customers may experience intermittent connectivity issues with NTP servers in the VPC, which could affect time synchronization for your instances.

Resolved: This incident has been resolved.

Investigating: Some customers may experience intermittent connectivity issues with NTP servers in the VPC, which could affect time synchronization for your instances.

Resolved: Issue is now solved. Between 2025-09-08 17:57 UTC and 22:34 UTC, one of our load balancers in front of our infrastructure was down. As a result, during that time frame, around 1/6th of the users on the fr-par region might have faced connectivity issues to their Serverless Function/Container (connection refused). The root cause has been identified, and a fix will be made soon to prevent this from happening again. We sincerely apologize for any inconvenience. Thanks for your understanding.

Investigating: We are continuing to investigate this issue.

Investigating: We have noticed several errors on containers that result in connection refusals. We are currently investigating in order to resolve this as quickly as possible.

Resolved: This incident has been resolved.

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

Identified: REDIS High Availability clusters (1 primary node + 1 standby node) are impacted.

The failover service is temporarily unavailable, and the creation of a Redis cluster in High Availability mode is also unavailable.

Other types of Redis clusters (standalone and 3-node clusters) are not impacted.

Existing High Availability clusters are not impacted as long as nothing causes a failover.

The issue has been identified by our engineers, and a fix is ​​underway.

Investigating: Since September 8, 2025, emails sent to Orange MXs may experience delays.

Identified: We are continuing to work on a fix for this issue.

Identified: Provisioning of the infrastructure powering managed inference deployments is currently impacted by increased latency. This may impact the time required to create and update deployments.

Resolved: Issue is now solved. Between 2025-09-08 17:57 UTC and 22:34 UTC, one of our load balancers in front of our infrastructure was down. As a result, during that time frame, around 1/6th of the users on the fr-par region might have faced connectivity issues to their Serverless Function/Container (connection refused). The root cause has been identified, and a fix will be made soon to prevent this from happening again. We sincerely apologize for any inconvenience. Thanks for your understanding.

Investigating: We are continuing to investigate this issue.

Investigating: We have noticed several errors on containers that result in connection refusals. We are currently investigating in order to resolve this as quickly as possible.

Resolved: This incident has been resolved.

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

Identified: REDIS High Availability clusters (1 primary node + 1 standby node) are impacted.

The failover service is temporarily unavailable, and the creation of a Redis cluster in High Availability mode is also unavailable.

Other types of Redis clusters (standalone and 3-node clusters) are not impacted.

Existing High Availability clusters are not impacted as long as nothing causes a failover.

The issue has been identified by our engineers, and a fix is ​​underway.

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

Investigating: We are experiencing some difficulties with DNS resolution via a private network. This only affects SRV records.

We are doing everything we can to resolve this quickly.

Identified: We are continuing to work on a fix for this issue.

Identified: Provisioning of the infrastructure powering managed inference deployments is currently impacted by increased latency. This may impact the time required to create and update deployments.

Resolved: Here is the list of affected racks in DC5 ROOM 7 : S7 D1 S7 D7 S7 D13 S7 D16 S7 D20 S7 D72 S7 C18 S7 C24 S7 C25 S7 C31

Monitoring: We experienced a network issue in a pod in DC5 for Elastic Metal, resulting in a brief disconnection. The issue has now been resolved.

Monitoring: Due to a hardware issue, some Elastic Metal instances experienced brief connectivity interruptions as BGP sessions between network devices were temporarily affected.

Resolved: This incident has been resolved.

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

Identified: REDIS High Availability clusters (1 primary node + 1 standby node) are impacted.

The failover service is temporarily unavailable, and the creation of a Redis cluster in High Availability mode is also unavailable.

Other types of Redis clusters (standalone and 3-node clusters) are not impacted.

Existing High Availability clusters are not impacted as long as nothing causes a failover.

The issue has been identified by our engineers, and a fix is ​​underway.

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

Investigating: We are experiencing some difficulties with DNS resolution via a private network. This only affects SRV records.

We are doing everything we can to resolve this quickly.

Resolved: This incident has been resolved.

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

Identified: REDIS High Availability clusters (1 primary node + 1 standby node) are impacted.

The failover service is temporarily unavailable, and the creation of a Redis cluster in High Availability mode is also unavailable.

Other types of Redis clusters (standalone and 3-node clusters) are not impacted.

Existing High Availability clusters are not impacted as long as nothing causes a failover.

The issue has been identified by our engineers, and a fix is ​​underway.

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

Investigating: We are experiencing some difficulties with DNS resolution via a private network. This only affects SRV records.

We are doing everything we can to resolve this quickly.

Resolved: This incident has been resolved.

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

Identified: REDIS High Availability clusters (1 primary node + 1 standby node) are impacted.

The failover service is temporarily unavailable, and the creation of a Redis cluster in High Availability mode is also unavailable.

Other types of Redis clusters (standalone and 3-node clusters) are not impacted.

Existing High Availability clusters are not impacted as long as nothing causes a failover.

The issue has been identified by our engineers, and a fix is ​​underway.

Resolved: This incident has been resolved.

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

Identified: REDIS High Availability clusters (1 primary node + 1 standby node) are impacted.

The failover service is temporarily unavailable, and the creation of a Redis cluster in High Availability mode is also unavailable.

Other types of Redis clusters (standalone and 3-node clusters) are not impacted.

Existing High Availability clusters are not impacted as long as nothing causes a failover.

The issue has been identified by our engineers, and a fix is ​​underway.

Resolved: This incident has been resolved.

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

Identified: REDIS High Availability clusters (1 primary node + 1 standby node) are impacted.

The failover service is temporarily unavailable, and the creation of a Redis cluster in High Availability mode is also unavailable.

Other types of Redis clusters (standalone and 3-node clusters) are not impacted.

Existing High Availability clusters are not impacted as long as nothing causes a failover.

The issue has been identified by our engineers, and a fix is ​​underway.

Resolved: This incident has been resolved.

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

Identified: REDIS High Availability clusters (1 primary node + 1 standby node) are impacted.

The failover service is temporarily unavailable, and the creation of a Redis cluster in High Availability mode is also unavailable.

Other types of Redis clusters (standalone and 3-node clusters) are not impacted.

Existing High Availability clusters are not impacted as long as nothing causes a failover.

The issue has been identified by our engineers, and a fix is ​​underway.

Resolved: This incident has been resolved.

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

Identified: REDIS High Availability clusters (1 primary node + 1 standby node) are impacted.

The failover service is temporarily unavailable, and the creation of a Redis cluster in High Availability mode is also unavailable.

Other types of Redis clusters (standalone and 3-node clusters) are not impacted.

Existing High Availability clusters are not impacted as long as nothing causes a failover.

The issue has been identified by our engineers, and a fix is ​​underway.

Resolved: This incident has been resolved.

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

Identified: REDIS High Availability clusters (1 primary node + 1 standby node) are impacted.

The failover service is temporarily unavailable, and the creation of a Redis cluster in High Availability mode is also unavailable.

Other types of Redis clusters (standalone and 3-node clusters) are not impacted.

Existing High Availability clusters are not impacted as long as nothing causes a failover.

The issue has been identified by our engineers, and a fix is ​​underway.

Resolved: Switch has been replaced. Services are up again.

Incident is resolved since 11:37 local-time.

Investigating: Servers attached to this switch are currently unreachable.

Monitoring: The high CPU usage on a router hosting DEDIBOX servers in fr-par-1 has been resolved. There was no impact on forwarding, and no side effects such as ARP or IPFO moves were observed.

Identified: Our network team will need to perform an emergency maintenance on this router the 12/09/2025 from 09:30AM UTC time to 10:30AM UTC.

You will experience a loss of public connectivity on your node hosted in dc2 room 101 racks N13 to N18, G20 to G37 and H20 to H22, during the maintenance window. Feel free to reach us if you need further assistance.

Thank you for your understanding.

Identified: The router health got worse over the night, ARP process on the device is now stuck and newer ARP entries can't be entered in the system, as such it is affecting the IPFO moves on the device. Our engineer are working on stabilizing the situation, it might come with an emergency maintenance.

Investigating: Since 5:00 PM CET, we have observed a high increase of CPU usage on a router hosting Dedibox servers in fr-par-1.

Server concerned : dc2 room 101 racks N13 to N18, G20 to G37 and H20 to H22

CPU usage is currently high but stable and no side effects are being observed, we will resume the operation to find the root cause of the issue during working hours

Investigating: Since 5:00 PM CET, we have observing a high increase of CPU usage on a router hosting DEDIBOX servers in fr-par-1. There is currently no impact on forwarding, but the router may experience side effects such as ARP or IPFO moves.

Resolved: Incident is finished since today 15:20 local-time.

Investigating: We are currently experiencing an issue with a server in our fr-par-1 data center, Room 101, Rack H37. This may affect the availability of some DEDIBOX servers hosted on this hardware.

We are investigating the cause and will provide updates as soon as possible.

Investigating: The IP address 51.159.208.135 of our DEDIBOX Classic Hosting is blacklisted by Microsoft.

Our team is investigating the situation.

Resolved: This incident has been resolved.

Investigating: Since Saturday, 13 September at 10 p.m. Paris time, we have noticed the first cases of difficulty accessing DC3's dedibackup. This may cause issues when trying to access or manage your backups. We are currently investigating the issue.

Investigating: The OneCloud API is currently unavailable, preventing users from ordering or managing their VPS.

We apologize for any inconvenience caused.

Monitoring: The high CPU usage on a router hosting DEDIBOX servers in fr-par-1 has been resolved. There was no impact on forwarding, and no side effects such as ARP or IPFO moves were observed.

Identified: Our network team will need to perform an emergency maintenance on this router the 12/09/2025 from 09:30AM UTC time to 10:30AM UTC.

You will experience a loss of public connectivity on your node hosted in dc2 room 101 racks N13 to N18, G20 to G37 and H20 to H22, during the maintenance window. Feel free to reach us if you need further assistance.

Thank you for your understanding.

Identified: The router health got worse over the night, ARP process on the device is now stuck and newer ARP entries can't be entered in the system, as such it is affecting the IPFO moves on the device. Our engineer are working on stabilizing the situation, it might come with an emergency maintenance.

Investigating: Since 5:00 PM CET, we have observed a high increase of CPU usage on a router hosting Dedibox servers in fr-par-1.

Server concerned : dc2 room 101 racks N13 to N18, G20 to G37 and H20 to H22

CPU usage is currently high but stable and no side effects are being observed, we will resume the operation to find the root cause of the issue during working hours

Resolved: Incident is finished since today 15:20 local-time.

Investigating: We are currently experiencing an issue with a server in our fr-par-1 data center, Room 101, Rack H37. This may affect the availability of some DEDIBOX servers hosted on this hardware.

We are investigating the cause and will provide updates as soon as possible.

Investigating: The OneCloud API is currently unavailable, preventing users from ordering or managing their VPS.

We apologize for any inconvenience caused.

Investigating: The OneCloud API is currently unavailable, preventing users from ordering or managing their VPS.

We apologize for any inconvenience caused.

Investigating: The OneCloud API is currently unavailable, preventing users from ordering or managing their VPS.

We apologize for any inconvenience caused.

Resolved: This incident has been resolved.

Investigating: All Dedibox servers in the block D are currently unreachable.

This may cause connectivity issues for the affected servers.

Our engineers are working to resolve this situation.

Investigating: The OneCloud API is currently unavailable, preventing users from ordering or managing their VPS.

We apologize for any inconvenience caused.