Scaleway Outage History
Scaleway degraded · 4 active incidents · 2 long-running issues View live status →Pingoru has recorded 363 incidents for Scaleway: 362 in the last 12 months and 133 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 36 | 646 of 720 (90%) |
| May 2026 | 45 | 723 of 744 (97%) |
| June 2026 | 60 | 575 of 720 (80%) |
| July 2026 | 65 | 654 of 744 (88%) |
| August 2026 | 34 | 572 of 744 (77%) |
| September 2026 | 47 | 720 of 720 (100%) |
| October 2026 | 44 | 590 of 590 (100%) |
Incidents, newest first
Notice July 28, 2026 [EM] [DDX] (PAR-1 DC2) Some servers are down on rack E6 room 103 1d 3h Dedibox, DC2, Elastic Metal, Serverless-Database
Started Jul 28, 2026, 10:16 AM UTC· resolved Jul 29, 2026, 01:42 PM UTC
- investigating Jul 28, 2026, 10:16 AM UTC
For an unknown reason, half of rack E6 room 103 is down (PAR1- DC2)
- investigating Jul 28, 2026, 12:33 PM UTC
We are continuing to investigate this issue.
- investigating Jul 28, 2026, 12:43 PM UTC
We are continuing to investigate this issue.
- resolved Jul 29, 2026, 01:42 PM UTC
This incident has been resolved.
Minor July 28, 2026 [Instances][POST MORTEM] - FR-PAR-1 - Issue with some PRO2 instances 2h
Started Jul 28, 2026, 05:00 AM UTC· resolved Jul 28, 2026, 07:00 AM UTC
- resolved Jul 30, 2026, 11:59 AM UTC
July 28, 2026 — 09:02 CEST: Our monitoring system detected connectivity issues affecting multiple PRO2 hypervisors in FR-PAR-1. Several servers appeared unreachable.
- postmortem Jul 30, 2026, 11:59 AM UTC
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.
Minor July 24, 2026 [DEDIBOX] [DC2]- 1 rack lost public connectivity 1h 25m Dedibox, DC2
Started Jul 24, 2026, 08:46 AM UTC· resolved Jul 24, 2026, 10:12 AM UTC
- investigating Jul 24, 2026, 08:46 AM UTC
Due to a network equipment failure, Dedibox servers in the following racks at the OPCORE datacenter are affected: - s202A-B7
- investigating Jul 24, 2026, 08:50 AM UTC
Due to a network equipment failure, Dedibox servers in the following racks at the OPCORE datacenter are affected: - s202A-B7
- resolved Jul 24, 2026, 10:12 AM UTC
The faulty switch has been replaced. Every server should now be reachable.
Minor July 24, 2026 [BMNA] - Certificate imap.bookmyname.com seems to be incorrect 6d BookMyName
Started Jul 24, 2026, 08:32 AM UTC· resolved Jul 30, 2026, 08:43 AM UTC
- investigating Jul 24, 2026, 08:32 AM UTC
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.
- resolved Jul 30, 2026, 08:43 AM UTC
This incident has been resolved.
Minor July 23, 2026 [API Gateway] - [it-mil] - connection failures 42m APIs
Started Jul 23, 2026, 02:41 PM UTC· resolved Jul 23, 2026, 03:23 PM UTC
- identified Jul 23, 2026, 02:41 PM UTC
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)
- resolved Jul 23, 2026, 03:23 PM UTC
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.
Notice July 23, 2026 [KAFK] - [fr-par] Interruption of service during an upgrade – fr-par-1, fr-par-2, fr-par-3, Kafka
Started Jul 23, 2026, 02:34 PM UTC· resolved Jul 23, 2026, 02:34 PM UTC
- resolved Jul 23, 2026, 02:34 PM UTC
[14:45] While upgrade our infra some of the clusters were unreachable
Notice July 22, 2026 [JOBS] - [fr-par] - Execution of some job runs was interrupted – Instances
Started Jul 22, 2026, 12:57 PM UTC· resolved Jul 22, 2026, 12:57 PM UTC
- resolved Jul 22, 2026, 12:57 PM UTC
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/2026 01:49:00 CEST and between 22/07/2026 03:44:00 CEST and 21/07/2026 05:30:00. The number of impacted job runs represent approximately the tenth of our average daily job runs. This is an informative status and no corrective action was required by us. Please check if you need to run your job again. We apologize for the inconvenience.
Minor July 22, 2026 [CAAS] - [fr-par] - namespaces and containers stuck in transient statuses 21m Serverless Container
Started Jul 22, 2026, 09:33 AM UTC· resolved Jul 22, 2026, 09:55 AM UTC
- identified Jul 22, 2026, 09:33 AM UTC
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 either: - updated between 2026-07-21 21:07 UTC and 2026-07-21 22:05 UTC - or deleted between 2026-07-21 21:33 UTC and 2026-07-22 03:18 UTC We have fixed the statuses, so resources are not stuck anymore. But, this would require impacted users to update or delete again their namespaces/containers if the status is in error with one of these error messages: - For previously "updating" containers: Last container update could not be processed successfully. Please try again - For previously "deleting" containers: Container could not be succesfully deleted. Please try again - For previously "updating" namespaces: Last namespace update could not be processed successfully. Please try again - For previously "deleting" namespaces: Namespace could not be succesfully deleted. Please try again Sorry about any inconvenience.
- resolved Jul 22, 2026, 09:55 AM UTC
Incident is now resolved. Please read instructions in the previous message if your container or namespace has one of the following error messages. Sorry again for any inconvenience.
Major July 21, 2026 [KUBERNETES] - [fr-par] - Product API down 7h 12m Kubernetes Kapsule
Started Jul 21, 2026, 09:43 PM UTC· resolved Jul 22, 2026, 04:56 AM UTC
- investigating Jul 21, 2026, 09:43 PM UTC
Product API is down for Kubernetes clusters
- monitoring Jul 22, 2026, 01:40 AM UTC
The Kapsule public API is available again.
- investigating Jul 22, 2026, 03:30 AM UTC
We are currently investigating this issue.
- monitoring Jul 22, 2026, 03:52 AM UTC
The situation has returned to normal
- resolved Jul 22, 2026, 04:56 AM UTC
This incident has been resolved.
Major July 21, 2026 [fr-par-1] - Issue with Compute Instances 7h 52m Databases, Instances, Kubernetes Kapsule, Serverless-Database
Started Jul 21, 2026, 09:03 PM UTC· resolved Jul 22, 2026, 04:55 AM UTC
- investigating Jul 21, 2026, 09:03 PM UTC
Following a crash of one node on the block storage cluster at 20h15 UTC, some VMs are stuck. The oncall team is investigating it.
- investigating Jul 21, 2026, 09:13 PM UTC
We are continuing to investigate this issue.
- investigating Jul 21, 2026, 09:39 PM UTC
We are still investigating this critical issue with the utmost priority.
- investigating Jul 21, 2026, 10:50 PM UTC
Our team is currently working on solving the issue.
- investigating Jul 21, 2026, 11:35 PM UTC
Disk I/O operations are starting to recover, which should begin resolving the issue for the instances.
- investigating Jul 22, 2026, 12:27 AM UTC
The situation is stable. All products are now operational except for the Kapsule public API, which is still unavailable.
- monitoring Jul 22, 2026, 01:41 AM UTC
The Kapsule public API is available again.
- investigating Jul 22, 2026, 03:30 AM UTC
We are currently investigating this issue.
- monitoring Jul 22, 2026, 03:53 AM UTC
The situation has returned to normal
- resolved Jul 22, 2026, 04:55 AM UTC
This incident has been resolved.
- postmortem Jul 22, 2026, 04:01 PM UTC
**Incident Overview** On July 21, a block storage cluster incident affected the Instance product on FR-PAR-1 between 20:14 and 03:45 UTC. This incident caused a regional service degradation \(FR-PAR\), resulting in the following impacts: * Kapsule operations were unavailable on a regional level between 21:30 and 01:30 UTC. * Instances on FR-PAR-1 were non-functional. * All managed products relying on Instance and Kapsule experienced disruptions. #### **Root Cause Analysis** **5 whys** * **Why were Instance and its dependent products unavailable?** Because disk I/O was impossible. * **Why was disk I/O impossible?** Because cluster doesn't accept I/O operations. * **Why cluster doesn’t accept I/O operations?** Due to a fault in a cluster component \(crash\). * **Why was a cluster component faulty?** It suffered an OOM \(Out of Memory\) kill. * **Why did an OOM kill occur?** The memory limit was incorrectly configured, causing the component to consume excessive memory and triggering an OS-level OOM kill. * **Why was the memory limit incorrectly configured?** The cluster hardware is heterogeneous; nodes have varying memory capacities. A global setting was applied without accounting for nodes with lower memory, leading to node-level OOM kills. * **Why was the configuration error not detected?** We lack sufficient safeguards for this specific configuration. ### Impact on Kapsule Product * **Why did an incident in a single Availability Zone \(AZ\) impact the entire FR-PAR region for Kapsule?**The Kapsule API was proactively disabled to prevent a cascading failure \("snowball effect"\) caused by auto-healing mechanisms reacting to widespread instance unavailability. * **Why is a multi-AZ product affected by a single API endpoint failure?**The Kapsule API architecture is currently regional and lacks the granularity to isolate or disable specific Availability Zones. Consequently, disabling the regional API was the necessary precautionary measure to protect block storage convergence. #### **Summary of Events** #### **Incident Timeline \(UTC\)** | **Time \(UTC\)** | **Event Description** | | --- | --- | | 20:14 UTC | OOM kill on one OSD | | 20:28 UTC | First alert on block storage team | | 20:43 UTC | Escalation to larger teams, incident open at company level | | 20:48 UTC | sbs-api stops processing river jobs \(no more volume update\) | | 21:30 UTC | API Kapsule is unavailable | | 21:43 UTC | First restart of blk-api \(internal api, not customer facing\) | | 22:27 UTC | Second restart of blk-api, helped unstick api calls | | 23:48 UTC | Faulty OSD removed from production, throughput restored on cluster | | 23:50 UTC | Teams begin relaunching operations on disk | | 00:00 UTC | System was unavailable | | 01:30 UTC | API Kapsule is available | | 02:08 UTC | Beginning of second block cluster global failure | | 03:45 UTC | Block Cluster state restored successfully, end of impact | #### **Resolution and Improvements** **Short-term Actions** * During the incident timelapse, we identified a configuration issue and corrected the memory limits across all cluster nodes. **Mid-term Actions** * Enhance cluster configuration management to prevent environment-specific mismatches \(e.g., node-level hardware heterogeneity\). * Implement isolation mechanisms to ensure that individual component failures do not impact the overall cluster stability. * We also notice network saturation during the recovery leading to latencies increase, we may need to rework this part. * Optimize network performance during recovery phases to prevent latency spikes caused by saturation. * Improve the incident response to avoid logical bias #### **Contact** If you have any further questions or need assistance, please contact our support team.
Minor July 21, 2026 [WBHE] - [fr-par] - inconsistencies in the database affecting free domain mappings 40m Web Hosting
Started Jul 21, 2026, 07:09 PM UTC· resolved Jul 21, 2026, 07:50 PM UTC
- investigating Jul 21, 2026, 07:09 PM UTC
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.
- resolved Jul 21, 2026, 07:50 PM UTC
This incident has been resolved since 19:15 UTC.
Minor July 20, 2026 [BLOCK-STORAGE][FR-PAR-1] - Block Storage High latencies on write operations 13h 20m fr-par-1, Block Storage
Started Jul 20, 2026, 07:07 PM UTC· resolved Jul 21, 2026, 08:28 AM UTC
- identified Jul 20, 2026, 07:07 PM UTC
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.
- resolved Jul 21, 2026, 08:28 AM UTC
This incident has been resolved.
Minor July 20, 2026 [API] - [it-mil-1] - Network issue API 15s APIs, it-mil-1
Started Jul 20, 2026, 02:50 PM UTC· resolved Jul 20, 2026, 02:51 PM UTC
- investigating Jul 20, 2026, 02:50 PM UTC
Following a network issue, the product APIs were unavailable for a few minutes. The issue was immediately resolved by our teams.
- resolved Jul 20, 2026, 02:51 PM UTC
This incident has been resolved.
Minor July 20, 2026 [Kapsule] - [All region] - Error 500 when creating pool 36m fr-par-1, fr-par-2, fr-par-3, nl-ams-1 and 7 more
Started Jul 20, 2026, 01:31 PM UTC· resolved Jul 20, 2026, 02:07 PM UTC
- investigating Jul 20, 2026, 01:31 PM UTC
Pool creation throw error 500 when trying to create new pool. Our team is investigating.
- identified Jul 20, 2026, 01:50 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Jul 20, 2026, 02:07 PM UTC
The issue has been resolved by our product team. Pools should now be created without any further issues.
Minor July 20, 2026 [API Gateway] - [fr-par-1] APIs increase of error rate in fr-par 1d 15h APIs, IAM
Started Jul 20, 2026, 10:13 AM UTC· resolved Jul 22, 2026, 01:33 AM UTC
- identified Jul 20, 2026, 10:13 AM UTC
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.
- resolved Jul 22, 2026, 01:33 AM UTC
This incident has been resolved.
Minor July 17, 2026 [Network infrastructure] - [DC5/PAR2] - unstable connection on one switch s1-a59.dc5 3h 14m Dedibox
Started Jul 17, 2026, 10:06 AM UTC· resolved Jul 17, 2026, 01:21 PM UTC
- investigating Jul 17, 2026, 10:06 AM UTC
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.
- resolved Jul 17, 2026, 01:21 PM UTC
This incident has been resolved.
Minor July 17, 2026 [Serverless SQL DB] - [fr-par1] - Slow cold starts 2d 23h Serverless-Database
Started Jul 17, 2026, 10:04 AM UTC· resolved Jul 20, 2026, 09:38 AM UTC
- investigating Jul 17, 2026, 10:04 AM UTC
Customers may encounter slowdowns in database cold starts, which can take up to 30 seconds.
- monitoring Jul 17, 2026, 03:36 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 20, 2026, 09:38 AM UTC
This incident has been resolved.
Minor July 17, 2026 [Apple Silicon] - [fr-par-1/fr-par-3(dc2/dc4)] - degraded service 1h 23m Apple Silicon
Started Jul 17, 2026, 07:32 AM UTC· resolved Jul 17, 2026, 08:56 AM UTC
- investigating Jul 17, 2026, 07:32 AM UTC
Due to a network incident under investigation, installation/reinstallation and reboot workflows via API or console are not available for Apple Silicon. Currently in use mac are still operationals and reachable.
- resolved Jul 17, 2026, 08:56 AM UTC
This incident has been resolved.
Notice July 16, 2026 [Cockpit] - [it-mil1] - Observability down for 1h – Cockpit
Started Jul 16, 2026, 12:33 PM UTC· resolved Jul 16, 2026, 12:33 PM UTC
- resolved Jul 17, 2026, 12:33 PM UTC
Due to NotReady node, we lost all ingestion on it-mil-1 for ~1h Start at 13h20 -> Ended at 14h20
Major July 16, 2026 [Virtual Cloud Servers] - [fr-par-2/DC5] Partial outages due to power loss 1h 47m Managed Inference
Started Jul 16, 2026, 04:23 AM UTC· resolved Jul 16, 2026, 06:11 AM UTC
- investigating Jul 16, 2026, 04:23 AM UTC
Customers may experience partial outages on their Virtual Cloud Servers due to a power loss on an internal dependency in fr-par-2/DC5.
Minor July 15, 2026 Login Issues Affecting Accounts with Multiple Organizations 15h 25m Account, Dedibox Console
Started Jul 15, 2026, 03:32 PM UTC· resolved Jul 16, 2026, 06:58 AM UTC
- investigating Jul 15, 2026, 03:32 PM UTC
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.
- investigating Jul 15, 2026, 03:37 PM UTC
We are continuing to investigate this issue.
- monitoring Jul 15, 2026, 04:30 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 16, 2026, 06:58 AM UTC
This incident has been resolved.
Minor July 15, 2026 [Cockpit] - [nl-ams] Ingestion errors on custom metrics 1d 21h Jobs, Serverless Container, Serverless Functions, Cockpit
Started Jul 15, 2026, 09:52 AM UTC· resolved Jul 17, 2026, 07:24 AM UTC
- investigating Jul 15, 2026, 09:52 AM UTC
Customers may experience gaps in logs from Scaleway products for the time range 10:30-12:00 CEST
- investigating Jul 15, 2026, 09:59 AM UTC
We are continuing to investigate this issue.
- resolved Jul 17, 2026, 07:24 AM UTC
This incident has been resolved.
Minor July 13, 2026 [Container Registry] - [world] - Missing tags on regional endpoints 13m Container Registry
Started Jul 13, 2026, 01:48 PM UTC· resolved Jul 13, 2026, 02:02 PM UTC
- identified Jul 13, 2026, 01:48 PM UTC
The issue has been found, fixed, tested and is being rolled out.
Minor July 12, 2026 [Network infrastructure] - [DC3] Room 4 4-6 rack 1 - Public switch is unreachable 1h 34m
Started Jul 12, 2026, 09:13 AM UTC· resolved Jul 12, 2026, 10:48 AM UTC
- investigating Jul 12, 2026, 09:13 AM UTC
Customers may experience a partial outage of public connectivity on servers attached to the public switch Room 4 4-6 rack 1 in DC3.
- resolved Jul 12, 2026, 10:48 AM UTC
This incident has been resolved.
Minor July 10, 2026 [Cockpit] - [fr-par] Traces ingestion and query degraded 1h 40m Cockpit
Started Jul 10, 2026, 01:10 PM UTC· resolved Jul 10, 2026, 02:50 PM UTC
- investigating Jul 10, 2026, 01:10 PM UTC
Customers may experience degraded performance when ingesting or querying traces in Cockpit in the fr-par region
- resolved Jul 10, 2026, 02:50 PM UTC
This incident has been resolved.