Scaleway Status

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.

We are continuing to investigate this issue.

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

This incident has been resolved.

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

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

Some customers are experiencing errors when using Grafana.

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

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

Today, from 04h48 to 04h50 UTC a block cluster hosting b_ssd volumes reported high latencies following a network issue affecting a server rack Cluster recovered at 04h51. Very few IO operations were still stuck until manual intervention at 05h10 UTC. Situation is normal since.

This incident has been resolved.

We are continuing to investigate this issue.

The issue is not limited to PAR2; it affects all regions on various operating systems. We are still investigating.

Customers may be experiencing boot issues after installing / rebooting their Elastic Metal server on PAR2. We are currently investigating.

Customers may experience connectivity issues with servers in rack B61 due to an unreachable switch in the network infrastructure.

This incident has been resolved.

Customers may experience connectivity issues on their VPS instances due to a networking issue on an internal component in the fr-par-1 region.

This incident has been resolved.

Customers may experience instabilities when using the mistral-medium-3.5-128b model in the fr-par region.

This incident has been resolved.

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

Customers may experience failures when creating dedicated deployments on the Generative APIs product in the fr-par region. The issue has been identified and our teams are working on a resolution.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

Customers may experience failures when creating dedicated deployments on the Generative APIs product in the fr-par region.

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

Customers may experience issues when pushing to Container Registry.

After an extended period of monitoring, we have confirmed that all systems are stable and fully operational.

We have resolved a certificate configuration issue that caused a communication outage between two of our internal components. All affected services are now fully restored and operating normally. Our team is actively monitoring the situation and implementing permanent changes to improve stability and prevent this specific issue from recurring. The incident was resolved at 10:47 UTC.

Some users may experience connectivity issues when accessing newly created resources in VPC. The incident started at 08:50 UTC. The problem has been identified, and we are actively working to resolve it.

Customers may experience connectivity issues with Edge Services due to a temporary outage of node servers.

Customers may have experienced delays when creating new batches in Generative APIs due to an internal dependency issue. The issue has been resolved and all batches are now being processed normally.

Customers may experience delays when creating new batches in Generative APIs due to an internal dependency issue. IAM managed application "scw-managed-genapi-batch" used within the batch system have been re created. Customers using S3 bucket policies may need to update their policy to take in account the new ApplicationID. The ApplicationId can be found after a first batch validation error

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

Customers may experience delays when creating new batches in Generative APIs due to an internal dependency issue.

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

Customers may experience connectivity issues with IPAM service in the Milan region due to an internal dependency.

This incident has been resolved.

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

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

Customers may experience issues when pushing to Container Registry

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

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.

This incident has been resolved.

Customers may experience loss of public connectivity on Kapsule and Kosmos due to loss of default route on fully isolated nodes. Running netplan apply on the node or triggering a reboot fixes the issue. We are currently investigating the issue.

This incident has been resolved.

Customers cannot set an organization address during account creation or for existing accounts due to an empty country selection dropdown.

This incident has been resolved.

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

Users cannot perform an identity verification on the console, preventing obtaining quota increase. The following error message appears when trying to perform a KYC: `Failed to connect to identity verification provider. Try again or contact Support.`

The root cause was due to a hardware issue on the switch. We will do a replacement in a near future. A separate maintenance will be created to prevent any further issue. All servers linked to this switch and racks are up and running.

The issue has now been resolved. All relevant teams are investigating the incident to determine the root cause and prevent similar issues in the future.

We are continuing to investigate this issue.

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 due to a unexpected network switch reboot.

Customers may experience connectivity issues with MySQL databases on pf-013 due to a storage capacity issue on an internal component.

This incident has been resolved.

Customers may experience connectivity issues on their websites hosted on pf-014.whm.fr-par.scw.cloud due to an internal dependency malfunction.

The DNS servers ns0.online.net (IPv4) for Dedibox domains and ns0.dom.scw.cloud (IPv4) for Scaleway domains are unreachable, but the other DNS servers remain available.

This incident has been resolved.

Following a defect on one of our switch, our authentication servers are currently unavailable. This impact the mail and databases access. Our engineers are currently investigating.

No more SMTP blacklist messages reported from Outlook provider.

Our service is currently experiencing disruption due to blacklisting by Microsoft. We are actively working with Microsoft to resolve this issue as soon as possible.

This incident has been resolved.

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

Customers may experience high load on Queues, Topics & Events in fr-par due to an internal component. We are currrently investigating this issue.

Between 2026-02-10 09:00 UTC and 2026-02-11 08:00 UTC, around 50% of container logs were not forwarded to users' cockpit. After investigation, a faulty reload of our logs collector caused the issue. After reloading, some logs might have been backfilled, but not the entirety. The issue is now fixed; sorry about any inconvenience.

This incident has been resolved.

Customers are unable to create corporate accounts through the Account API. we are currently investigating this issue.

This incident has been resolved.

Customers may experience failing CRUD operations on deployments for Generative APIs in fr-par due to instabilities on an internal component. Active deployments are unaffected unless updated.

Customers may experience connectivity issues on MongoDB public endpoints due to a flap on an internal component.

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

Customers may experience network congestion between Paris and Amsterdam due to a partial loss of redundancy on the RPN network.

Customers may experience connectivity issues in the it-mil-1 zone due to a DHCP service disruption.