Scaleway Status

Resolved: This incident has been resolved.

Monitoring: A fix have been deployed and we are monitoring the situation.

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

Investigating: Some customers are experiencing errors when using Grafana.

Resolved: Following a component overload in Cockpit during an upgrade designed to improve its resilience, difficulties integrating logs and metrics arose from Scaleway products between 11.30 am and 3.30 pm.

There may have been a partial loss of this data.

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

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

Monitoring: Between 11:50 a.m. and 1:30 p.m., metrics ingestion on FR-PAR was affected due to an operation performed on one of the components to improve its resilience. Metrics and log data are also affected.

Resolved: Since 10:30 UTC, customers may experience issues retrieving their product logs to Cockpit due to an internal dependency failure in the nl-ams region. Logs are not ingested anymore, so it seems logs are lost forever.

Investigating: The incident primarily affects NL-AMS, while FR-PAR is also experiencing some loss of metrics and logs. PL-WAW is not impacted.

Investigating: The same component that was experiencing issues earlier this week on Cockpit is now experiencing problems across several regions. The fix implemented has not fully resolved the overload at this entry point for logs and metrics. An update is currently being rolled out and should restore data ingestion. Some metrics and logs may have been lost.

Monitoring: The last fixes have been deployed and our infrastructure dimensioned properly on nl-ams.

The situation have improved but we keep monitoring the situation.

Identified: The same component that was experiencing issues earlier this week on Cockpit is now experiencing problems across several regions. The fix implemented has not fully resolved the overload at this entry point for logs and metrics.

After the update rolled out yesterday, we are still observing some issues with log and metric ingestion in NL‑AMS & FR-PAR. We are actively working on fixing the problem.

Monitoring: We scaled the infrastructure and added more observability to tackle this recurring performance issue. We'll monitor the situation closely.

Identified: Customers may experience issues when pushing to Container Registry.

Resolved: This incident has been resolved.

Investigating: Customers may experience delays when provisioning new Managed Database instances or performing operations that require infrastructure changes in the fr-par region due to an issue with an internal dependency.

Resolved: Everything is back to normal. Services are up and running. If you are still encountering an issue, please contact our support team.

Monitoring: During routine maintenance, a new configuration was deployed to our backbone routers managing traffic for fr-par-2. An unforeseen configuration conflict resulted in a total loss of public connectivity (blackholing) for all Elastic Metal servers.

The configuration was pushed at 08:42 UTC for both IPv4 and IPv6. IPv4 was rollback at 09:20 and IPv6 was rollback at 09:45, restoring all connectivity.

Monitoring: The fix has been deployed. Services are up and running. We are monitoring the situation and we will provide more information.

Identified: The root cause has been found. A fix is being deployed.

Investigating: Customers may experience a partial outage of public network connectivity on Elastic Metal servers in PAR2 (DC5).

Identified: Customers may experience transient 5xx errors when using the gemma4-26b-a4b-it model due to instabilities on an internal component.

The problem has been identified and we are working on a fix. Retrying the requests after a short delay will succeed.

Identified: We are working on a fix. Instabilities may still appear when using mistral-medium-3.5-128b model. But overall the service remain usable.

Investigating: Customers may experience instabilities when using the mistral-medium-3.5-128b model in the Generative APIs service in the fr-par region.

Resolved: This incident has been resolved.

Monitoring: The situation is back to nominal state, the root cause has been identified and incident responses are back to normal.

Identified: Part of our Mistral Small 3.2 infrastructure start becoming un stable with un usual error rates.

Resolved: Observability volumes are increasing, and we are reaching some limits with serverless log ingestion. We have resized the cache for our ingestion components, and we plan to deploy smart features to this component this week.

Investigating: We are continuing to investigate this issue.

Investigating: A small subset of Scaleway Product logs/metrics might be unavailable on fr-par on small time-range

Yesterday : 9:20 - 11h30 CEST Today : 17:20 - ongoing CEST

Resolved: This incident has been resolved.

Investigating: Customers may experience partial outages when managing Kafka resources due to an issue on the control plane.

Resolved: The issue has been resolved and monitoring data is now being collected as expected.

Monitoring: Customers may experience missing monitoring data for NATS, Queues, Topics & Events in the fr-par region.

Resolved: Servers have been moved to a different location and brought back online. All objects, including one-zone objects should be accessible.

Investigating: Due to abnormal temperature, some storage nodes are being shutdown to prevent data loss. This will impact acces to some objects with one-zone storage class

Resolved: Observability volumes are increasing, and we are reaching some limits with serverless log ingestion. We have resized the cache for our ingestion components, and we plan to deploy smart features to this component this week.

Investigating: We are continuing to investigate this issue.

Investigating: A small subset of Scaleway Product logs/metrics might be unavailable on fr-par on small time-range

Yesterday : 9:20 - 11h30 CEST Today : 17:20 - ongoing CEST

Monitoring: We scaled the infrastructure and added more observability to tackle this recurring performance issue. We'll monitor the situation closely.

Identified: Customers may experience issues when pushing to Container Registry.

Resolved: Observability volumes are increasing, and we are reaching some limits with serverless log ingestion. We have resized the cache for our ingestion components, and we plan to deploy smart features to this component this week.

Investigating: We are continuing to investigate this issue.

Investigating: A small subset of Scaleway Product logs/metrics might be unavailable on fr-par on small time-range

Yesterday : 9:20 - 11h30 CEST Today : 17:20 - ongoing CEST

Investigating: Customers may experience issues registering or validating domains on Transactional Email due to a validation error on an internal component.

Investigating: Customers may experience degraded performance on their websites and email services hosted on the pf-012 platform due to high load on an internal component.

Monitoring: We scaled the infrastructure and added more observability to tackle this recurring performance issue. We'll monitor the situation closely.

Identified: Customers may experience issues when pushing to Container Registry.

Resolved: This incident has been resolved.

Investigating: Customers may experience delays when provisioning new Managed Database instances or performing operations that require infrastructure changes in the fr-par region due to an issue with an internal dependency.

Monitoring: We scaled the infrastructure and added more observability to tackle this recurring performance issue. We'll monitor the situation closely.

Identified: Customers may experience issues when pushing to Container Registry.

Resolved: Everything is back to normal. Services are up and running. If you are still encountering an issue, please contact our support team.

Monitoring: During routine maintenance, a new configuration was deployed to our backbone routers managing traffic for fr-par-2. An unforeseen configuration conflict resulted in a total loss of public connectivity (blackholing) for all Elastic Metal servers.

The configuration was pushed at 08:42 UTC for both IPv4 and IPv6. IPv4 was rollback at 09:20 and IPv6 was rollback at 09:45, restoring all connectivity.

Monitoring: The fix has been deployed. Services are up and running. We are monitoring the situation and we will provide more information.

Identified: The root cause has been found. A fix is being deployed.

Investigating: Customers may experience a partial outage of public network connectivity on Elastic Metal servers in PAR2 (DC5).

Resolved: This incident has been resolved.

Investigating: Customers may experience delays when provisioning new Managed Database instances or performing operations that require infrastructure changes in the fr-par region due to an issue with an internal dependency.

Resolved: Servers have been moved to a different location and brought back online. All objects, including one-zone objects should be accessible.

Investigating: Due to abnormal temperature, some storage nodes are being shutdown to prevent data loss. This will impact acces to some objects with one-zone storage class

Monitoring: We scaled the infrastructure and added more observability to tackle this recurring performance issue. We'll monitor the situation closely.

Identified: Customers may experience issues when pushing to Container Registry.

Resolved: This incident has been resolved.

Investigating: Customers may experience delays when provisioning new Managed Database instances or performing operations that require infrastructure changes in the fr-par region due to an issue with an internal dependency.

Resolved: This incident has been resolved.

Identified: Start time : 13h20

Rooms experienced a Cooling issue specifically, impacting temperature at Amsterdam\AMS-1 with potential impact to customers in AMS-1.D05, AMS-1.D06 and AMS-1.D07. Our team is currently investigating.

If you experience any issues, please open an Incident ticket through the Customer Portal or contact the GNOC to receive further details and automated updates. We apologize for any inconvenience.

Thank you,

Investigating: Some customers may have experienced network connectivity issues in

AMS1 Room H6 Rack 6.12.17 6.12.29 6.12.60 6.12.67 and 6.12.71 to 6.12.75

We are investigating to know the root cause linked to this reboot.

Monitoring: Situation is now stable, we are closely monitoring situation on both members of HA pair.

Monitoring: Customers may experience iSCSI connection failures on Dedibox RPN-SAN HA HDD-18 in DC2/DC3. The issue has been identified and is currently being monitored. We apologize for any inconvenience caused and will provide further updates as soon as possible.

Investigating: Customers may iSCSI connections failures on Dedibox RPN-SAN HA HDD-18.