Scaleway Incident History

The servers have been put back into production and latencies are now nominal as of August 5, 6:30 PM CEST.

August 5: From 2 p.m. to 6:30 p.m. CEST: Due to complications during scheduled hardware maintenance, some object storage servers were temporarily offline. During this period, customers may have experienced higher p99 latencies. Service availability was otherwise maintained.

Some customers cannot access Grafana. We are investigating.

We have identified that the product Public Gateway creation/update in fr-par-1 were stuck in a transient state. The incident has been mitigated.

[05:00] Increase of query load broke store gateways.

Everything has been stable again since 18:28 UTC. yesterday. The incident is closed.

We are continuing to monitor for any further issues.

The incident has now been mitigated.

We are continuing to investigate this issue.

We are investigating performance degradation affecting Block Storage in the fr-par region. Our engineering teams are actively working to identify the root cause. We will provide further updates as more information becomes available.

Switch s43-c9.rpn.dc3 is down. There is no RPN connection for the servers in DC3, room 4-3, rack C9

This incident has been resolved, and all servers should now be reachable.

We have detected a switch down in DC2 room 205 rack E1 Servers in that rack currently have no public network access and are unreachable.

Between approximately 15:00 and 15:45 CEST on 3 August, a Web Hosting platofrm pf-014 in fr-par experienced intermittent unavailability, resulting in HTTP errors and slow responses for websites hosted on it. Other servers in the Web Hosting fleet were unaffected. The cause was identified and has been corrected. The server remains under close monitoring.

This incident has been resolved.

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

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

July 28, 2026 — 09:02 CEST: Our monitoring system detected connectivity issues affecting multiple PRO2 hypervisors in FR-PAR-1. Several servers appeared unreachable. July 28, 2026 — 09:14 CEST: The Scaleway Instances team began investigating the issue. July 28, 2026 — 09:14 CEST: Initial findings showed that the affected servers were still operational, but network traffic was being disrupted. July 28, 2026 — 09:16 CEST: An internal incident was opened, and the Network team joined the investigation. July 28, 2026 — 09:32 CEST: One of the two leaf switches showed uplink issues. However, part of the traffic was still being forwarded through the affected switch. July 28, 2026 — 09:35 CEST: We disabled the hypervisor ports connected to the faulty leaf switch to force all traffic through the redundant switch. July 28, 2026 — 09:35 CEST: Connectivity was restored for the affected instances. July 28, 2026 — 09:37 CEST: Logs from the faulty leaf switch showed that several ports went down, followed by one of its power supply units and then its uplinks. This sequence of events caused traffic black hole. July 28, 2026 — 09:38 CEST: We also identified multiple power supply alerts affecting several hypervisors in the same rack. July 28, 2026 — 09:44 CEST: A ticket was opened with our data center provider to request an electrical inspection of the rack. July 28, 2026 — 11:19 CEST: While reviewing the equipment logs, we identified a protective shutdown on one switch following a temperature alert. However, no abnormal temperature readings were detected by the other sensors in the rack. July 28, 2026 — 11:21 CEST: The data center provider performed a visual inspection and found no visible issues with the rack. July 28, 2026 — 15:09 CEST: The faulty component responsible for the incident was identified. A defective power supply unit caused electrical disruptions across the rack, triggering temperature alerts, power supply alerts on other devices, and the loss of several links on one leaf switch. July 29, 2026 — 14:21 CEST: All faulty components were replaced. The network connections that had been disabled were re-enabled. The service was fully restored and remained stable.

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

This incident has been resolved.

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

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

This incident has been resolved.

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.

The Transactional Email services have been running without any issue for a few hours, and we were able to partially retrieve webhook events for the last 15 days. Webhooks sent from 2026-07-29 13:10:28.678436+02 to 2026-07-29 17:23:09 UTC are definitively lost. To prevent further issues, the new webhook events retention has been lowered to 15 days.

Service up again, but could suffer from latency, we are monitoring the situation. Unfortunately, the webhook event data history are currently lost.

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

This incident has been resolved.

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.

This incident has been resolved.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

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

This incident has been resolved.

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

This incident has been resolved.

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

We are currently investigating this issue.

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

The faulty switch has been replaced. Every server should now be reachable.

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

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

The situation has been back to normal since 3:15 PM. Pushes to the registry and container deployments in the IT-mil region are working again. Sorry about any inconvenience.

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)

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