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
Object Storage services in the fr-par region have returned to normal operating conditions following the deployment of the fix. Our teams continue to closely monitor the infrastructure to ensure service stability before marking the incident as resolved.
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
identified
Following an infrastructure deployment, connectivity was disrupted across several racks, potentially impacting Object Storage customers in the fr-par region through increased latency and request errors. The issue has been identified, and our engineering teams are currently deploying a fix to restore normal service operations.
[Generative API] - [global] - Bge-multilingual-gemma-2 became unavailable
A fix has been implemented and we are monitoring the results.
investigating
We are currently experiencing degraded performance with it-mil APIs. Some requests may see elevated latency, intermittent errors, or timeouts. Our engineering team is actively investigating the issue and working to restore normal service as quickly as possible.
A fix has been implemented and we are monitoring the results.
identified
19th October from 2:30pm to 7pm
Some requests to the deepseek-v4.1-flash model have experienced elevated timeouts.
We have implemented a mitigation, and error rates are improving. We're monitoring the situation.
[Serverless-Database]- [fr-par] - slow cold start for the DB and DB in status error
Since Saturday October 18, 2026 at 07:55 UTC (09:55 Paris time), Serverless SQL Databases as occured slow cold start for the DB and DB in status error.
Temperatures are decreasing following an intervention by our service provider.
investigating
Servers in room 108 experience temperature increase.
This lead to CPU throttling and may result into unreachable instance.
We are working with our datacenter provider to fix the situation.
Timeouts are observed on qwen3-embedding-8b model through the Generative API.
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.
June 2026
[WebHosting Elements] - [fr-par] High load on pf-012 platform
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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.
The situation is back to nominal state, the root cause has been identified and incident responses are back to normal.
identified
Part of our Mistral Small 3.2 infrastructure start becoming un stable with un usual error rates.
[Object Storage] - [fr-par-2] - Thermal shutdown for several storage pods
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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
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.
[Cockpit]-[fr-par] - memory pressure on product-frontend
minorSource not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
monitoring
We are continuing to monitor for any further issues.
monitoring
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.
Metrics and log data are also affected.
[NATS, Queues, Topics & Events] - [fr-par] Monitoring data missing
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Customers may experience missing monitoring data for NATS, Queues, Topics & Events in the fr-par region.
[Dedibox RPN-SAN] - [DC2/DC3] Storage failures on SAN HA pair HDD-18
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Situation is now stable, we are closely monitoring situation on both members of HA pair.
monitoring
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.
investigating
Customers may iSCSI connections failures on Dedibox RPN-SAN HA HDD-18.
[Kafka] - [fr-par] Control plane partial outage
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience partial outages when managing Kafka resources due to an issue on the control plane.
[Network infrastructure] - [DC5][PAR-2] Public network issue
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
monitoring
The fix has been deployed. Services are up and running. We are monitoring the situation and we will provide more information.
identified
The root cause has been found. A fix is being deployed.
investigating
Customers may experience a partial outage of public network connectivity on Elastic Metal servers in PAR2 (DC5).
[DC5] - Switch unreachable in rack B61
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience connectivity issues with servers in rack B61 due to an unreachable switch in the network infrastructure.
