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.
May 2026
[Cockpit] - [world] Unable to disable Alertmanager
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers are unable to disable their Alertmanager configuration in Cockpit.
[Instance Orchestration] - it-mil-1 - Instances API unavailability
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
Due to an internal dependency issue, customers will experience unavailability of the Instances API in the it-mil-1 region
[EM Labs] - [fr-par-2] RV-1 server boot loop issue
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue has been fixed. Servers are no longer stuck in a boot loop state.
We are still monitoring the situation and ensuring that our fix will work long‑term.
investigating
Since Friday, after the DC5 operator room electrical incident.
EM-RV1 seems to be stuck in a boot loop, unable to boot successfully from the network.
In the meantime, do not reboot your system
Also, you will not be able to create new EM-RV1 server and booting them
[Serverless Containers] - [fr-par] Instability on one cluster
Source not attested
Last archived state: resolved
View archived record details
monitoring
Everything has returned to normal for the impacted cluster.
We are continuing to monitor the situation to ensure everything is fine.
investigating
Customers may experience instability on one of our six Serverless Containers clusters in the fr-par region.
[Data Warehouse] - [fr-par] - API not reachable
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience connectivity issues with the Data Warehouse API in the fr-par region due to an internal dependency.
[Cockpit] - [fr-par] Latencies on query/ingestion on external logs
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience latencies on query and ingestion of external logs in the fr-par region due to an internal dependency issue.
Customers are unable to create new SQS/NATS triggers for Serverless Functions in the fr-par region. Serverless Containers are unaffected.
FR-PAR-2 connectivity loss
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
Datacenter teams are now confident the batteries were involved in the initial incident, they will attempt to switch back to main power at 14:30 CEST.
monitoring
Batteries replacement has been completed on all 4 electrical paths.
Removed batteries are under tests and investigations to confirm their involvement in the initial incident.
No more action on production expected for now.
We are still on power generators for the time being.
monitoring
Batteries replacement is ongoing, 1 of the 4 electrical paths has been done (no impact).
Datacenter teams will proceed with the next paths.
monitoring
The datacenter provider has planned an intervention on Saturday at 10:30 CEST to replace batteries on the electrical paths that had issues today.
This operation will be done live and should have no impact.
Once replaced, old batteries will be inspected and tested to confirm they were the cause of the incident.
Power will be kept on generators during this operation and after until the root cause is fully confirmed
monitoring
Updated status for impacted products:
- Object Storage: Everything back to normal
- Serveless containers and functions: Everything is back to normal.
- File: some instances may encounter troubles with their File Storage, we invite customers to restart their instances/nodes if affected
As the failover malfunction has not been diagnosed at this time, our datacenter manager will keep the affected elements under a generator.
monitoring
Updated status for impacted products:
- Object Storage: still some latency issues and timeout on connecting some buckets
- Serveless containers and functions: Everything is back to normal. Situation recovered and stable since 02:40 PM
- File Storage: some instances may encounter troubles with their File Storage, we invite customers to restart their instances/nodes if affected
monitoring
Updated status for impacted products:
- Kapsule: everything back to normal
- Databases: everything back to normal
- Object Storage: still some latency issues and timeout on connecting some buckets
- Serveless containers and functions: might face connection timeout issues when contacting their applications
- File Storage: some instances may encounter troubles with their File Storage, we invite customers to restart their instances/nodes if affected
monitoring
Clarification: only network rooms are running on power generators, with enough fuel for a few days
monitoring
Updated status for impacted products:
- Instances: everything back to normal
- Kapsule: same status
- Databases: same status
- Object Storage: same status
- Serveless containers and functions: might face connection timeout issues when contacting their applications
identified
As the power failure root cause is not yet understood (datacenter is investigating with its providers), we encourage you to shift workload on alternatives regions/AZ if possible.
identified
Datacenter informs us that we are running on power generators for now until the root cause is identified
monitoring
Teams are working on the recovery. Here is the status of impacted products:
- Instances: you may encounter issues with l_ssd/block snapshots or volumes
- Kapsule: Control planes are reachable and in nominal state, you may need to verify that your controllers reconnected properly on the apiservers. You may have experienced node replacement due to the autoheal or autoscaling process, this may delay volume re-attachments.
- Databases: snapshots may be blocked, some failovers have been starte...
monitoring
Datacenter hosting FR-PAR-2 availability zone occured a complete power failure in operator rooms during a planned datacenter maintenance.
Both operator rooms (network connectivity) were powerless for a few minutes leading to a complete isolation of the availability zone during the issue. We are investigating with the datacenter provider to understand the root cause.”
monitoring
Most services recovered and our teams are mobilized to recover the rest on fr-par-2. Root cause is a power issue in datacenter.
Other service on par1 & par3 were impacted during the service transition.
investigating
The issue is impacting multiple products on FR-PAR.
investigating
We are continuing to investigate this issue and searching for the root cause.
investigating
We are currently experiencing connection and network issues in the FR‑PAR region, affecting all FR‑PAR availability zones on Scaleway as well as DC5 on Dedibox.
Kafka cluster not reachable - Connection to Kafka clusters fails.
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating on that incident.
[API Gateway] - [world] APIs instabilities
majorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience Network issues contacting our APIs. We are currently investigating this issue.
