Daily provider-status observations and published incident history for Scaleway.
Regional incident
Scaleway has an active regional incident; no global outage is indicated. Verified .
Official provider source.
Looking for an update now? Check the current status, or follow Scaleway for future changes.
0%of 56 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
0%
30
30
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
A hardware issue impacted a RPN node (dc2-7) from 17/09/26 12h11 UTC to 18/09/26 13h01.
The service is now up for the clients using this node
We are monitoring closely for any new issues on the node and may need another downtime if the hardware issue persist.
The issue should be resolved in most destinations, our team is taking the necessary steps to ensure it works everywhere.
investigating
We are currently investigating a network issue affecting instances with an IP address in the 78.232.0.0/21 range. Outbound traffic from these instances may fail to reach a significant part of the internet. Our teams are actively working on it and we will provide an update as soon as we have more information.
The incident began on September 15 at 5:00 p.m. UTC+1
Processing of current tickets may take longer than usual. Our teams are currently working to restore the service as soon as possible. Thank you for your understanding.
Due to an issue with our phone system, only ticket and live chat assistance are currently available.
We are currently investigating the situation and will update this status as soon as we have more information.
At 3:45 am. CEST on 11/09/2026, the public switch located in DC2, room S103, rack A7, has rebooted.
All servers attached to it have lost public connectivity for around 10 minutes.
[09/09 - 16:50]
The Gemma 4 models started to show un usual latencies resulting in requests timeout
[10/09 - 9:00]
The incident has been mitigated and response times are back to normal
Legacy Incident Archive
223 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
[Key Manager] - [fr-par] Request timeouts due to migration issue
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue has been fixed at 1:20 pm.
Sorry for the inconvenience caused.
monitoring
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.
identified
We are continuing to work on a fix for this issue.
identified
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
Customers may experience request timeouts on the Key Manager service due to a migration issue on an internal component.
June 2026
[Generative APIs] - BatchAPI is down
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
BatchAPI is currently down due to an issue with an internal component.
[COCKPIT] - [fr-par/pl-waw] - Scaleway Metrics/Logs ingestion down
Source not attested
Last archived state: resolved
View archived record details
monitoring
We applied and monitored today the last fix for high RAM consumption. All seems fine now on Cockpit performances for all regions.
monitoring
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
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
[Container Registry] - [fr-par] Push slowness and errors
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
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.
[Instance Orchestration] - [fr-par-1] Compute metrics lost on AZ
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience missing compute metrics on Instance Orchestration due to a failure on an internal component.
[Transactional Email] - [fr-par-2] Sending delays due to internal component restart
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience delays in sending transactional emails due to a prolonged restart of an internal component.
[Generative APIs] - [all] gemma4-26b-a4b-it model instabilities
minorSource not attested
Last archived state: resolved
View archived record details
identified
We are still working on a fix. We will deploy the fix this week and it should resolve this matter.
identified
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.
[AMS1] - Cooling Incident
minorSource not attested
Last archived state: resolved
View archived record details
identified
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,
The last fixes have been deployed and our infrastructure dimensioned properly on nl-ams.
The situation have improved but we keep monitoring the situation.
identified
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.
The incident primarily affects NL-AMS, while FR-PAR is also experiencing some loss of metrics and logs. PL-WAW is not impacted.
investigating
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.
An update is currently being rolled out and should restore data ingestion. Some metrics and logs may have been lost.
