Scaleway reports multiple service issues

This incident has been resolved.

Newly restored instances will not be affected by this issue. Impacted customers will be contacted individually with updates regarding the corrective maintenance on their snapshots.

Customers may experience degraded performance when ingesting or querying traces in Cockpit in the fr-par region

The connectivity issues affecting Serverless Containers in the nl‑ams region occurred between 07:40 CET and 09:30 CET. As of 09:30 CET, the service is stable and fully reachable. If you still experience any problems, please contact our Support team. Thank you for your patience.

This incident has been resolved.

This incident has been resolved.

We are continuing to investigate this issue.

Update: Connectivity has been partially restored at around 9:30 AM. We are monitoring the situation.

Customers may experience longer deployment creation times on Managed Inference in fr-par

Starting from 07:30 CET, users may experience connectivity issues or failed requests when accessing their Serverless Containers in the nl-ams region. This issue is under investigation by our team.

Starting from 07:30 CET, users may experience connectivity issues or failed requests when accessing their Serverless Containers in the nl-ams region. This issue is under investigation by our team.

This incident has been resolved.

This incident has been resolved.

Customers may experience unresponsiveness when using the mistral-medium-3.5-128b model due to an instability on an internal component.

This incident has been resolved.

Maintenance for security system update. A downtime of 10 min can be expected during the maintenance Date/time: July 9th from 16h to 17h

Customers may experience failures when creating Spark clusters in the fr-par region due to an issue with an internal dependency.

This incident has been resolved.

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

Since 08/07 15H11 UTC Object storage customers experienced connectivity issues with Object Storage on it-mil-1. This was a routing issue and a fix was implemented at 08H26 UTC. Situation is back to normal.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

Customers may experience a partial outage on public connectivity for a few minutes due to a reboot of the public switch s301-b5-2 in DC2.

Since 08/07 16H UTC customers may experience connectivity issues with Object Storage on it-mil-1.

Customers may be unable to connect to their Dedibox VPS in the Paris location due to a locked state.

Customers may experience connectivity issues with Object Storage on it-mil-1.

This incident has been resolved.

This incident has been resolved.

Customers may be unable to create new deployments due to a lack of available IP addresses on the MSGQ service in the fr-par region.

This incident has been resolved.

[~17h] Customers may experience a high amount of 503 errors on Edge Services pipelines with Object Storage backends due to DNS resolution issues on an internal component.

This incident has been resolved.

Customers may experience failures when creating SEDB deployments due to a certificate-related error on an internal dependency.

Customers may experience service unavailability on Object Storage in it-mil-1 due to a routing issue.

This incident has been resolved.

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

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

This incident has been resolved.

Servers continue to operate normally. However, customers may experience failures when attempting to reboot servers in rescue mode or perform install, reinstall, clean, and reset operations due to an incompatibility with an internal dependency.

Customers may experience high latencies on File Storage in fr-par-1, we are currently investigating this issue.

This incident has been resolved.

This incident has been resolved.

Instances that were restored through snapshots can produce new snapshots, but cannot restore those snapshots. We are currently investigating this issue.

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

We are currently experiencing an issue in the ams1 zone affecting the creation and upgrading of Public Gateways. Existing online gateways are not affected. Our engineering team is actively investigating, and we will provide updates as they become available.

This incident has been resolved.

Customers may experience high latencies on File Storage in fr-par-1 due to an internal component issue. The issue has been identified and resolved. We are monitoring the situation to ensure stability.

Customers may experience high latencies on File Storage in fr-par-1 due to an internal component issue.

The issue has been found and fixed. Duplicate billing emails were sent, especially during the domain direct purchase. Actual charges were processed only once.

Customers may receive duplicate email notifications for their purchase orders.

Customers may experience transient 5xx errors when using the qwen3.6-35b-a3b model due to instabilities on an internal component.

The last fixes have been deployed and our infrastructure dimensioned properly on nl-ams. The situation have improved but we keep monitoring the situation.

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.