Scaleway Status

Identified: We did discover that the trouble is broader than we thought. As a first mitigation we do recommend that users wait before upgrading from aws v1 (we do recommand any version strictly prior to aws-cli 1.37.0 or boto3 < 1.36.0). If aws v2 (that we do not recommend for the moment) is mandatory, we do recommend using aws-cli < 2.23.0 We are working actively to support those new versions, and plan to release fixes for the end of next week. The details of the bug are : support of CRC64NVME does not work properly Tranfer-Encoding: chunked header does not work

Identified: Everyone using aws-cli versions versions v1: >=1.37.0 and v2: >=2.23.0 received a 400 errors on PUT and POST requests.

Investigating: aws-cli now enforces a CRC64NVME integrity checksum on all PUT and POST requests. This concerns the versions v1: >=1.37.0 and v2: >=2.23.0. We do not currently support this checksum, we are working on how best to handle it on our end. In the meantime, you can choose one of these options to keep your aws-cli request working:

• Use the --checksum-algorithm option with one of our supported checksums:
  • SHA1
  • SHA256
  • CRC32
  • CRC32C
• Use an older version of aws-cli, this way it will not enforce the CRC64NVME checksum

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.

Resolved: This incident has been resolved.

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

Investigating: Apple Mails services blacklist our ASN, we are currently in contact with them to solved the issue.

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.

Resolved: This incident has been resolved.

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

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

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

Identified: The issue has been identfied and a fix is being prepared

Investigating: The IP 51.159.128.65 of our Webhosting platform pf-1007 is blacklisted by Microsoft. We are currently working on it.

Resolved: This incident has been resolved.

Monitoring: Our engineers installed a new fix this morning and the service has been back up and running since 9am.

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

Investigating: Some website and their database are unavailable on the PF 1010. The webhosting team has been alerted and will investigate it as soon as possible.

Investigating: Cockpit query path is degraded Some client may faced errors for query that fetch more than 12h of data.

Resolved: This incident has been resolved.

Identified: During the weekend, Microsoft blacklisted one of our shared IPs, we blocked the IP and are currently investigating.

Investigating: Since Feb 20th at 11, metrics from the NATS, Queues, Topic and Events products are not stored in cockpit.

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

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.

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

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

Identified: The issue has been identfied and a fix is being prepared

Investigating: Cockpit query path is degraded Some client may faced errors for query that fetch more than 12h of data.

Resolved: This incident has been resolved.

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

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

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

Identified: The issue has been identfied and a fix is being prepared

Investigating: Cockpit query path is degraded Some client may faced errors for query that fetch more than 12h of data.

Resolved: This incident has been resolved.

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

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

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

Identified: The issue has been identfied and a fix is being prepared

Investigating: Cockpit query path is degraded Some client may faced errors for query that fetch more than 12h of data.

Resolved: RPN switch rebooted at DC2, room 101 101, rack K37 and L37. The service was down for a few minutes from 2025 Feb 18 11:33 UTC to 11:39 UTC., we apologize for the inconvenience.

Resolved: Data center: DC3, Room: 4 4-5, Rack: D9 The public switch has been restarted. We have no public service on the servers connected to this switch for a few minutes from February 19 23:11 UTC to 23:16 UTC.

RPN is not impacted.

Resolved: This incident has been resolved.

Investigating: No PUB service on servers connected to this switch for a few minutes from 2025 Feb 20 09:37 UTC to 09:39 UTC. RPN not impacted.

Investigating: No PUB and RPN service on servers connected to this switch for a few minutes from 2025 Feb 21 10:59 UTC to 11:09 UTC. PUB and RPN both impacted. Switch impacted:

• DC2, Salle : 101 101, Baie : G36, Bloc : A
• DC2, Salle : 101 101, Baie : G30, Bloc : N
• DC2, Salle : 101 101, Baie : G35, Bloc : B

Investigating: No PUB and RPN service on servers connected to this switch for a few minutes from 2025 Feb 21 10:59 UTC to 11:09 UTC. PUB and RPN both impacted.

Resolved: No RPN service on servers connected to this switch for 5 minutes from 2025 Feb 18 04:38 UTC to 04:43 UTC.

Investigating: No PUB and RPN service on servers connected to this switch for a few minutes from 2025 Feb 21 10:59 UTC to 11:09 UTC. PUB and RPN both impacted. Switch impacted:

• DC2, Salle : 101 101, Baie : G36, Bloc : A
• DC2, Salle : 101 101, Baie : G30, Bloc : N
• DC2, Salle : 101 101, Baie : G35, Bloc : B

Investigating: No PUB and RPN service on servers connected to this switch for a few minutes from 2025 Feb 21 10:59 UTC to 11:09 UTC. PUB and RPN both impacted.

Resolved: Data center: DC3, Room: 4 4-5, Rack: D9 The public switch has been restarted. We have no public service on the servers connected to this switch for a few minutes from February 19 23:11 UTC to 23:16 UTC.

RPN is not impacted.

Resolved: This incident has been resolved.

Investigating: No PUB service on servers connected to this switch for a few minutes from 2025 Feb 20 09:37 UTC to 09:39 UTC. RPN not impacted.