Scaleway Status

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.

Identified: The root cause is identified. A fix is being reviewed.

Investigating: The unavailability of the Rescue mode also slows down the Support's diagnosis.

Investigating: Elastic metal recently put on Rescue mode cannot boot on disk anymore. Our team is already investigating this issue. We recommand to not activate Rescue mode for now.

Investigating: We are currently investigating this 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: The 9th January, between 18:15 and 18:45 UTC, we experienced network instability issues that caused intermittent disruptions to some of our databases. The issue has been resolved.

Investigating: Scaleway products' metrics ingestion suffered downtime between 11/12 1:05AM and 12/12 9:35AM. Some metrics may not have been properly ingested in this period and won't be available. A fix has already been deployed

Investigating: We have detected an issue on Grafana it may give 500 errors.

The issue has been forwarded to our team for resolution.

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

Identified: There is an ongoing fiber cut incident between amsterdam & paris, we are offloading the traffic to avoid saturation of communication between the 2 regions. There potentially will be an increase of latency between regions.

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

Identified: There is an ongoing fiber cut incident between amsterdam & paris, we are offloading the traffic to avoid saturation of communication between the 2 regions. There potentially will be an increase of latency between regions.

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

Identified: There is an ongoing fiber cut incident between amsterdam & paris, we are offloading the traffic to avoid saturation of communication between the 2 regions. There potentially will be an increase of latency between regions.

Resolved: The 9th January, between 18:15 and 18:45 UTC, we experienced network instability issues that caused intermittent disruptions to some of our databases. The issue has been resolved.

Identified: There is an ongoing fiber cut incident between amsterdam & paris, we are offloading the traffic to avoid saturation of communication between the 2 regions. There potentially will be an increase of latency between regions.

Resolved: The 9th January, between 18:15 and 18:45 UTC, we experienced network instability issues that caused intermittent disruptions to some of our databases. The issue has been resolved.

Identified: There is an ongoing fiber cut incident between amsterdam & paris, we are offloading the traffic to avoid saturation of communication between the 2 regions. There potentially will be an increase of latency between regions.

Resolved: The 9th January, between 18:15 and 18:45 UTC, we experienced network instability issues that caused intermittent disruptions to some of our databases. The issue has been resolved.

Identified: There is an ongoing fiber cut incident between amsterdam & paris, we are offloading the traffic to avoid saturation of communication between the 2 regions. There potentially will be an increase of latency between regions.

Resolved: Following the deployment of a new configuration, 5 servers connected to a switch lost connection to the RPN network for a minute. Location of the switch is -4/C5/PARDC3. The incident is totally resolved now.

Investigating: The IP/smtpauth.online.net 51.159.208.135 is blacklisted by Microsoft. We are currently working on it.

Resolved: Following the deployment of a new configuration, 5 servers connected to a switch lost connection to the RPN network for a minute. Location of the switch is -4/C5/PARDC3. The incident is totally resolved now.

Resolved: Following the deployment of a new configuration, 5 servers connected to a switch lost connection to the RPN network for a minute. Location of the switch is -4/C5/PARDC3. The incident is totally resolved now.

Monitoring: Maintenance was in progress, causing the outage. We apologize for the inconvenience, do not hesitate to contact our support team if you encounter any issue.

Investigating: We are currently investigating this issue.