Scaleway

Some actions cannot be applied on Instances on fr-par-1, resulting in resources stucks in a transient state.

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

At 15h55, public switch s45-d14.dc3 has rebooted; public network connectivity was affected for 10 minutes for all servers attached to it.

First response

First response after about 0 min

Progress

1 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Some instability and a down of the service, our team is in investigation to resolve the issue

First response

First response after about 0 min

Progress

3 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Installations may result in errors, and changing to rescue mode may fail in the NL-AMS-2 region specifically. We are currently investigating the issue.

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Our service TEM has been down since 10:20 CEST It was resolved at 10:52 CEST

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Multiple products unavailable between 11:45 UTC and 12:00 UTC annotation audit trail cockpit containers datalab datawarehouse instance v1 k8s kafka kms mongo registry secrets

First response

First response after about 0 min

Progress

4 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Users might experiment infinite loops in responses in case of multi turn tool_call requests using model gemma-4-26b-a4b-it

First response

First response after about 0 min

Progress

3 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

For an unknown reason, half of rack E6 room 103 is down (PAR1- DC2)

First response

First response after about 0 min

Progress

4 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

July 28, 2026 — 09:02 CEST: Our monitoring system detected connectivity issues affecting multiple PRO2 hypervisors in FR-PAR-1. Several servers appeared unreachable.

First response

First response after about 2h

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Due to a network equipment failure, Dedibox servers in the following racks at the OPCORE datacenter are affected: - s202A-B7

First response

First response after about 0 min

Progress

3 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

We are currently investigating an issue with the SSL certificates on imap.bookmyname.com and smtp.bookmyname.com. This issue may prevent some users from sending or receiving emails through these endpoints.

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Since around 1 PM UTC, some internal connections to Scaleway API on it-mil region started to fail. As a result: -Pushes to rg.it-mil.scw.eu are failing with HTTP 500 -Serverless Containers deployments are failing (resources stuck in creating) -etc. (list is not exhaustive)

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

[14:45] While upgrade our infra some of the clusters were unreachable

First notice

Announced when maintenance started

Progress

1 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

During compute instances incident on fr-par (cf. this status: https://status.scaleway.com/incidents/bsp2y5fysy9w), some jobs were interrupted during execution or were not executed at all. They ended in an Interrupted state with a reason technical_error. This happened intermittantly and only form some job runs only between 21/07/2026 22:00:00 CEST and 22/07/2…

First response

First response after about 0 min

Progress

1 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Following incident on Compute instances (https://status.scaleway.com/incidents/bsp2y5fysy9w), a few Serverless Containers and namespaces on fr-par region have been stuck in transient statuses (updating/deleting) during the night. Not all resources were impacted, only a fraction on one part of our infrastructure (~1/10). On this part, impacted resources were…

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Product API is down for Kubernetes clusters

First response

First response after about 0 min

Progress

5 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Following a crash of one node on the block storage cluster at 20h15 UTC, some VMs are stuck. The oncall team is investigating it.

First response

First response after about 0 min

Progress

11 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Some free domains may currently display a default hosting page or resolve incorrectly due to inconsistencies in domain mappings. Our teams are investigating and working to restore the correct configuration.

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Since around 12:30 PM UTC, several internal connections to the Scaleway API within the it-mil region are failing. As a result: - Pushes to rg.it-mil.scw.eu are failing and returning an "HTTP 500" error. - Serverless Containers deployments are failing (resources stuck in creating) (list is not exhaustive) Our team is actively working on a fix as we speak, we…

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

A mandatory maintenance operation targeting one of the Block Storage is taking longer than planned. Some clients may experience latencies during write operations on sbs_5k and sbs_15K volumes. We are monitoring it and working to tune this operation to limit impact.

First notice

Announced when maintenance started

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Following a network issue, the product APIs were unavailable for a few minutes. The issue was immediately resolved by our teams.

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Pool creation throw error 500 when trying to create new pool. Our team is investigating.

First response

First response after about 0 min

Progress

3 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

11:13 CEST to 11:48 CEST Users may have experienced high error rates or timeouts during this 30-minute window. Our engineering team has identified and resolved the issue.

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

A dedibox switch in DC5, room 1, rack A59 has an unstable connection to the upstream router. We need to replace the SFPs. This will result in a brief loss of connectivity for servers connected to this switch.

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Customers may encounter slowdowns in database cold starts, which can take up to 30 seconds.

First response

First response after about 0 min

Progress

3 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Installation/reinstallation and reboot workflows via API or console are not available for Apple Silicon. Currently in use mac are still operationals and reachable.

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Due to NotReady node, we lost all ingestion on it-mil-1 for ~1h Start at 13h20 -> Ended at 14h20

First response

First response after about 0 min

Progress

1 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

We are investigating an issue affecting login for some accounts that have multiple organizations linked to them. Accounts with a single organization are not impacted.

First response

First response after about 0 min

Progress

4 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Customers may experience gaps in logs from Scaleway products for the time range 10:30-12:00 CEST

First response

First response after about 0 min

Progress

3 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Customers may experience missing tags when listing tags on Container Registry regional endpoints. Pulling images by tag or digest is not impacted. The Container Registry API is not impacted and returns the correct list of tags.

First response

First response after about 0 min

Progress

4 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Customers may experience a partial outage of public connectivity on servers attached to the public switch Room 4 4-6 rack 1 in DC3.

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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.

First response

First response after about 0 min

Progress

3 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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

First notice

Announced when maintenance started

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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

First response

First response after about 0 min

Progress

3 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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.

First response

First response after about 0 min

Progress

1 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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

First response

First response after about 0 min

Progress

7 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Today, between 9:12 AM and 10:15 AM (Paris time), customers experienced a high number of HTTP 503 errors on Edge Services pipelines with Object Storage backends due to DNS resolution issues affecting an internal component. This incident has now been resolved, and our teams are continuing to monitor the situation.

First response

First response after about 0 min

Progress

1 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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.

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

[~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.

First response

First response after about 0 min

Progress

1 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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

First notice

Announced when maintenance started

Progress

3 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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

First response

First response after about 0 min

Progress

2 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

Customers may experience slowness and errors when pulling/pushing images to the Container Registry in fr-par. Some pulls/pushes may take up to 30 minutes or fail entirely. This may also cause delays or failures in Serverless Containers and Functions deployments.

First response

First response after about 0 min

Progress

4 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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.

First response

First response after about 0 min

Progress

3 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source

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

First response

First response after about 0 min

Progress

4 public update(s)

Data impact

Unknown

Compensation & remedy

Not mentioned by source