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 | 592 of 592 (100%) |
Incidents, newest first
Minor July 2, 2026 [Cockpit] - [fr-par] Difficulties querying Scaleway Metrics 2h 32m Cockpit
Started Jul 02, 2026, 08:01 AM UTC· resolved Jul 02, 2026, 10:34 AM UTC
- investigating Jul 02, 2026, 08:01 AM UTC
Customers may experience difficulties querying Scaleway Metrics older than 12 hours.
Minor July 2, 2026 [Block Storage - BSSD] - [fr-par-2] High latency on volumes – Block Storage, Object Storage
Started Jul 02, 2026, 07:57 AM UTC· resolved Jul 02, 2026, 07:57 AM UTC
- resolved Jul 02, 2026, 07:57 AM UTC
Customers may experience high latency on Block Storage volumes (only bssd) in the fr-par-2 region due to a slow response from an internal component.
Minor July 1, 2026 [Key Manager] - [fr-par] Request timeouts due to migration issue 5d Secret Manager
Started Jul 01, 2026, 09:48 AM UTC· resolved Jul 06, 2026, 09:49 AM UTC
- identified Jul 01, 2026, 09:48 AM UTC
Customers may experience request timeouts on the Key Manager service due to a migration issue on an internal component.
- identified Jul 01, 2026, 09:57 AM UTC
Creations and deletions on Key Manager and Secret Manager may fail for some clients. Access to keys and secrets is not impacted. Our team is investigating the issue.
- identified Jul 01, 2026, 09:58 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Jul 01, 2026, 11:37 AM UTC
Customers may experience request timeouts on the Key Manager service due to a migration issue on an internal component. The issue is currently being monitored and we are working to resolve it as quickly as possible. We apologize for any inconvenience this may cause.
- monitoring Jul 01, 2026, 12:33 PM UTC
The issue has been fixed at 1:20 pm. Sorry for the inconvenience caused.
- resolved Jul 06, 2026, 09:49 AM UTC
This incident has been resolved.
Minor June 30, 2026 [Network infrastructure] - [DC3] RPN switch rebooted – RPN
Started Jun 30, 2026, 02:06 PM UTC· resolved Jun 30, 2026, 02:06 PM UTC
- resolved Jun 30, 2026, 02:06 PM UTC
Customers in DC3 may experience a short unavailability of RPN connectivity due to an RPN switch reboot.
Minor June 30, 2026 [Block Storage] - [fr-par-1] Latency spikes on volumes 30s Block Storage
Started Jun 30, 2026, 10:41 AM UTC· resolved Jun 30, 2026, 10:42 AM UTC
- investigating Jun 30, 2026, 10:41 AM UTC
Customers may have experienced latency spikes on Block Storage volumes in par1cl02.
- resolved Jun 30, 2026, 10:42 AM UTC
This incident has been resolved.
Major June 30, 2026 [Generative APIs] - BatchAPI is down 19h 6m Generative API
Started Jun 30, 2026, 08:55 AM UTC· resolved Jul 01, 2026, 04:01 AM UTC
- investigating Jun 30, 2026, 08:55 AM UTC
BatchAPI is currently down due to an issue with an internal component.
- monitoring Jun 30, 2026, 10:55 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 01, 2026, 04:01 AM UTC
This incident has been resolved.
Notice June 30, 2026 [COCKPIT] - [fr-par/pl-waw] - Scaleway Metrics/Logs ingestion down 8d 3h Cockpit
Started Jun 30, 2026, 08:23 AM UTC· resolved Jul 08, 2026, 12:20 PM UTC
- monitoring Jun 30, 2026, 08:23 AM UTC
Cockpit impacted this night betwen 1am30 and 8am30 with data loss for all Products metrics and logs on FR-PAR & PL-WAW Regions Root cause : based on last week Cockpit ingestion solution, a high RAM consumption saturated nodes and corrupted replay solution. Status : Cockpit fixed at 8am30 and fix in development to avoid replay corruption on OOM events
- monitoring Jul 03, 2026, 01:21 PM UTC
Root cause was finally identified yesterday evening, we make an evolution on staging environments and monitored its behavior today. We plan to deploy this fix next monday morning. Metrics & Logs acquisition are fine since yesterday with a scaling workaround, we keep this solution for the week-end to not impact production on a friday afternoon.
- monitoring Jul 06, 2026, 04:17 PM UTC
We applied and monitored today the last fix for high RAM consumption. All seems fine now on Cockpit performances for all regions.
- resolved Jul 08, 2026, 12:20 PM UTC
This incident has been resolved.
Minor June 30, 2026 [Container Registry] - [fr-par] Push slowness and errors 15d 11h Container Registry, Serverless Container, Serverless Functions
Started Jun 30, 2026, 06:00 AM UTC· resolved Jul 15, 2026, 05:20 PM UTC
- investigating Jun 30, 2026, 11:58 AM UTC
Customers may experience slowness and errors when pushing images to the Container Registry in fr-par. Some pushes may take up to 30 minutes or fail entirely. This may also cause delays or failures in Serverless Functions deployments.
- investigating Jun 30, 2026, 02:42 PM UTC
We are continuing to investigate this issue.
- investigating Jul 02, 2026, 08:04 AM UTC
We are continuing to investigate this issue.
- resolved Jul 15, 2026, 05:20 PM UTC
This incident has been resolved.
Minor June 30, 2026 [Instance Orchestration] - [fr-par-1] Compute metrics lost on AZ 1d 6h Observability
Started Jun 30, 2026, 05:42 AM UTC· resolved Jul 01, 2026, 12:31 PM UTC
- investigating Jun 30, 2026, 05:42 AM UTC
Customers may experience missing compute metrics on Instance Orchestration due to a failure on an internal component.
- resolved Jul 01, 2026, 12:31 PM UTC
The incident is fully solved since around 7h30 UTC on 2026-06-30. It was a side-effect of https://status.scaleway.com/incidents/0vtzpl5bklrh where cockpit metrics were lost on fr-par/pl-waw. There should have been no impact on your infrastructure.
Minor June 29, 2026 [Transactional Email] - [fr-par-2] Sending delays due to internal component restart 17m Transactional Email
Started Jun 29, 2026, 03:00 PM UTC· resolved Jun 29, 2026, 03:17 PM UTC
- investigating Jun 29, 2026, 03:00 PM UTC
Customers may experience delays in sending transactional emails due to a prolonged restart of an internal component.
- resolved Jun 29, 2026, 03:17 PM UTC
This incident has been resolved.
Minor June 27, 2026 [Generative APIs] - [all] gemma4-26b-a4b-it model instabilities 12d Generative API
Started Jun 27, 2026, 01:07 PM UTC· resolved Jul 09, 2026, 01:30 PM UTC
- identified Jun 27, 2026, 01:07 PM UTC
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.
- identified Jul 06, 2026, 08:14 AM UTC
We are still working on a fix. We will deploy the fix this week and it should resolve this matter.
- resolved Jul 09, 2026, 01:30 PM UTC
This incident has been resolved.
Minor June 26, 2026 [AMS1] - Cooling Incident 18m nl-ams-1
Started Jun 26, 2026, 01:11 PM UTC· resolved Jun 26, 2026, 01:30 PM UTC
- identified Jun 26, 2026, 01:11 PM UTC
Start time : 13h20 Attention IMDC Customer, IMDC has experienced a Cooling issue specifically, impacting temperature at Amsterdam\AMS-1 with potential impact to customers in AMS-1.D05, AMS-1.D06 and AMS-1.D07. Our team is currently investigating. If you experience any issues, please open an Incident ticket through the Customer Portal or contact the GNOC to receive further details and automated updates. We apologize for any inconvenience. Thank you,
- resolved Jun 26, 2026, 01:30 PM UTC
This incident has been resolved.
Minor June 26, 2026 [Cockpit] - [nl-ams] [fr-par] Product logs unavailable 12d 2h Cockpit
Started Jun 26, 2026, 09:35 AM UTC· resolved Jul 08, 2026, 12:22 PM UTC
- identified Jun 26, 2026, 09:35 AM UTC
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.
- monitoring Jun 26, 2026, 04:05 PM UTC
The last fixes have been deployed and our infrastructure dimensioned properly on nl-ams. The situation have improved but we keep monitoring the situation.
- resolved Jul 08, 2026, 12:22 PM UTC
This incident has been resolved.
Minor June 25, 2026 [WebHosting Elements] - [fr-par] High load on pf-012 platform 5d 23h Web Hosting
Started Jun 25, 2026, 09:42 AM UTC· resolved Jul 01, 2026, 09:40 AM UTC
- investigating Jun 25, 2026, 09:42 AM UTC
Customers may experience degraded performance on their websites and email services hosted on the pf-012 platform due to high load on an internal component.
- resolved Jul 01, 2026, 09:40 AM UTC
This incident has been resolved.
Minor June 25, 2026 [GAPI] - [fr-par2] - mistral-small-3.2 errors rate increasing 16m Generative API
Started Jun 25, 2026, 09:20 AM UTC· resolved Jun 25, 2026, 09:37 AM UTC
- identified Jun 25, 2026, 09:20 AM UTC
Part of our Mistral Small 3.2 infrastructure start becoming un stable with un usual error rates.
- monitoring Jun 25, 2026, 09:31 AM UTC
The situation is back to nominal state, the root cause has been identified and incident responses are back to normal.
- resolved Jun 25, 2026, 09:37 AM UTC
This incident has been resolved.
Minor June 24, 2026 [Object Storage] - [fr-par-2] - Thermal shutdown for several storage pods 18h 19m fr-par-2, Object Storage
Started Jun 24, 2026, 03:45 PM UTC· resolved Jun 25, 2026, 10:05 AM UTC
- investigating Jun 24, 2026, 03:45 PM UTC
Due to abnormal temperature, some storage nodes are being shutdown to prevent data loss. This will impact acces to some objects with one-zone storage class
- resolved Jun 25, 2026, 10:05 AM UTC
Servers have been moved to a different location and brought back online. All objects, including one-zone objects should be accessible.
Minor June 24, 2026 [RDB] - [fr-par] Managed Database provisioning delays 16h 49m fr-par-1, fr-par-2, fr-par-3, Databases
Started Jun 24, 2026, 03:11 PM UTC· resolved Jun 25, 2026, 08:01 AM UTC
- investigating Jun 24, 2026, 03:11 PM UTC
Customers may experience delays when provisioning new Managed Database instances or performing operations that require infrastructure changes in the fr-par region due to an issue with an internal dependency.
- resolved Jun 25, 2026, 08:01 AM UTC
This incident has been resolved.
Minor June 24, 2026 [Cockpit]-[fr-par] - memory pressure on product-frontend 3h 21m Cockpit
Started Jun 24, 2026, 11:47 AM UTC· resolved Jun 24, 2026, 03:08 PM UTC
- monitoring Jun 24, 2026, 11:47 AM UTC
Between 11:50 a.m. and 1:30 p.m., metrics ingestion on FR-PAR was affected due to an operation performed on one of the components to improve its resilience.
- monitoring Jun 24, 2026, 12:50 PM UTC
We are continuing to monitor for any further issues.
- identified Jun 24, 2026, 12:52 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Jun 24, 2026, 03:08 PM UTC
Following a component overload in Cockpit during an upgrade designed to improve its resilience, difficulties integrating logs and metrics arose from Scaleway products between 11.30 am and 3.30 pm. There may have been a partial loss of this data.
Notice June 23, 2026 [NATS, Queues, Topics & Events] - [fr-par] Monitoring data missing 7h 30m Messaging and Queuing
Started Jun 23, 2026, 08:03 AM UTC· resolved Jun 23, 2026, 03:34 PM UTC
- monitoring Jun 23, 2026, 08:03 AM UTC
Customers may experience missing monitoring data for NATS, Queues, Topics & Events in the fr-par region.
- resolved Jun 23, 2026, 03:34 PM UTC
The issue has been resolved and monitoring data is now being collected as expected.
Major June 23, 2026 [Dedibox RPN-SAN] - [DC2/DC3] Storage failures on SAN HA pair HDD-18 8d 2h SAN
Started Jun 23, 2026, 06:56 AM UTC· resolved Jul 01, 2026, 09:35 AM UTC
- investigating Jun 23, 2026, 06:56 AM UTC
Customers may iSCSI connections failures on Dedibox RPN-SAN HA HDD-18.
- monitoring Jun 23, 2026, 03:01 PM UTC
Customers may experience iSCSI connection failures on Dedibox RPN-SAN HA HDD-18 in DC2/DC3. The issue has been identified and is currently being monitored. We apologize for any inconvenience caused and will provide further updates as soon as possible.
- monitoring Jun 23, 2026, 03:03 PM UTC
Situation is now stable, we are closely monitoring situation on both members of HA pair.
- resolved Jul 01, 2026, 09:35 AM UTC
This incident has been resolved.
Minor June 22, 2026 [Kafka] - [fr-par] Control plane partial outage 1h 3m Kafka
Started Jun 22, 2026, 01:34 PM UTC· resolved Jun 22, 2026, 02:38 PM UTC
- investigating Jun 22, 2026, 01:34 PM UTC
Customers may experience partial outages when managing Kafka resources due to an issue on the control plane.
- resolved Jun 22, 2026, 02:38 PM UTC
This incident has been resolved.
Critical June 22, 2026 [Network infrastructure] - [DC5][PAR-2] Public network issue 3h 1m fr-par-2, Elastic Metal
Started Jun 22, 2026, 09:23 AM UTC· resolved Jun 22, 2026, 12:24 PM UTC
- investigating Jun 22, 2026, 09:23 AM UTC
Customers may experience a partial outage of public network connectivity on Elastic Metal servers in PAR2.
- identified Jun 22, 2026, 10:02 AM UTC
The root cause has been found. A fix is being deployed.
- monitoring Jun 22, 2026, 10:08 AM UTC
The fix has been deployed. Services are up and running. We are monitoring the situation and we will provide more information and a post mortem once the incident is fully resolved.
- monitoring Jun 22, 2026, 10:21 AM UTC
During routine maintenance, a new configuration was deployed to our backbone routers managing traffic for fr-par-2. An unforeseen configuration conflict resulted in a total loss of public connectivity (blackholing) for all Elastic Metal servers. The configuration was pushed at 08:42 UTC for both IPv4 and IPv6. IPv4 was rollback at 09:20 and IPv6 was rollback at 09:45, restoring all connectivity.
- resolved Jun 22, 2026, 12:24 PM UTC
Everything is back to normal. Services are up and running. If you are still encountering an issue, please contact our support team.
Notice June 21, 2026 [Block Storage] - [fr-par-2] - Latencies on b_ssd volumes due to a network issue –
Started Jun 21, 2026, 04:30 AM UTC· resolved Jun 21, 2026, 04:30 AM UTC
- resolved Jun 21, 2026, 06:28 AM UTC
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.
Minor June 20, 2026 [PAR2] - Boot issue after installing an elastic metal 2h 58m fr-par-2, Elastic Metal
Started Jun 20, 2026, 06:58 PM UTC· resolved Jun 20, 2026, 09:56 PM UTC
- investigating Jun 20, 2026, 05:29 PM UTC
Customers may be experiencing boot issues after installing / rebooting their Elastic Metal server on PAR2. We are currently investigating.
- investigating Jun 20, 2026, 06:58 PM UTC
The issue is not limited to PAR2; it affects all regions on various operating systems. We are still investigating.
- investigating Jun 20, 2026, 09:56 PM UTC
We are continuing to investigate this issue.
- resolved Jun 20, 2026, 09:56 PM UTC
This incident has been resolved.
Minor June 19, 2026 [DC5] - Switch unreachable in rack B61 29m DC5
Started Jun 19, 2026, 12:54 PM UTC· resolved Jun 19, 2026, 01:23 PM UTC
- investigating Jun 19, 2026, 12:54 PM UTC
Customers may experience connectivity issues with servers in rack B61 due to an unreachable switch in the network infrastructure.