Scaleway Status

Investigating: S3 checksum error in some client/sdk, we alway return the full object checksum even when the request is ranged, causing issue in some high-level wrappers that try to compare the range's checksum with the full object one.

Full integrity of the objects aren't impacted, and all computed checksum are valid.

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.

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 investigating this issue.

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

Identified: The IP 51.159.208.135 of our Webhosting platform is blacklisted by Microsoft. We are currently working on it.

Resolved: This incident has been resolved.

Investigating: The issue has been identified at around 3pm (CET). We are currently investigating it.

Resolved: This incident has been resolved.

Investigating: Increasing number of 502 error. Our team is working to solve this problem.

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

Resolved: This incident has been resolved.

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

Investigating: We are currently investigating this issue.

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

Resolved: Uplink configuration has been updated and corrected. The situation is resolved. Please contact Support if the issue persists.

Identified: We have detected a switch down in room 101-k31-2. Servers in that rack currently have no public network access and are unreachable.

===================

17/06/25 09H00 UTC Issue has been forwarded to our team for resolution.

Resolved: This incident has been resolved.

Identified: The power on most of the chassis was recovered, we are booting the remaining customer nodes.

Identified: These rack are still impacted by this issue: h2-dv5 h2-ee14 h2-ee17 h2-ee18 h2-ee19 h2-ee20 h2-ee21 h2-ee24 h2-ee25 h2-ee26 h2-ee28 h2-ee29 h2-ee2h2 h2-ee30 h2-ee31

Our teams are working on the resolution.

Identified: We have detected a switch down in Hall 2 E-E, Baie : E30. Servers in that rack currently have no public network access and are unreachable since 18/06/2025 05h30.

The issue has been forwarded to our team for resolution.

Investigating: We are currently investigating this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

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

Identified: The IP 51.159.208.135 of our Webhosting platform is blacklisted by Microsoft. We are currently working on it.

Resolved: Uplink configuration has been updated and corrected. The situation is resolved. Please contact Support if the issue persists.

Identified: We have detected a switch down in room 101-k31-2. Servers in that rack currently have no public network access and are unreachable.

===================

17/06/25 09H00 UTC Issue has been forwarded to our team for resolution.

Investigating: We are currently investigating this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Identified: The power on most of the chassis was recovered, we are booting the remaining customer nodes.

Identified: These rack are still impacted by this issue: h2-dv5 h2-ee14 h2-ee17 h2-ee18 h2-ee19 h2-ee20 h2-ee21 h2-ee24 h2-ee25 h2-ee26 h2-ee28 h2-ee29 h2-ee2h2 h2-ee30 h2-ee31

Our teams are working on the resolution.

Identified: We have detected a switch down in Hall 2 E-E, Baie : E30. Servers in that rack currently have no public network access and are unreachable since 18/06/2025 05h30.

The issue has been forwarded to our team for resolution.

Resolved: This incident has been resolved.

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

Identified: Due to exceptional circumstances, the response time is slowed down. Sorry for the inconvenience