Update - 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
May 22, 2026 - 16:30 CEST
Update - 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
May 22, 2026 - 14:26 CEST
Update - Clarification: only network rooms are running on power generators, with enough fuel for a few days
May 22, 2026 - 13:25 CEST
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
May 22, 2026 - 13:10 CEST
Update - 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.
May 22, 2026 - 12:44 CEST
Identified - Datacenter informs us that we are running on power generators for now until the root cause is identified
May 22, 2026 - 12:31 CEST
Update - 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 started for HA
- Object storage: you may encounter some latencies
May 22, 2026 - 12:28 CEST
Update - 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.”
May 22, 2026 - 12:24 CEST
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.
May 22, 2026 - 11:42 CEST
Update - The issue is impacting multiple products on FR-PAR.
May 22, 2026 - 11:23 CEST
Update - We are continuing to investigate this issue and searching for the root cause.
May 22, 2026 - 11:21 CEST
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.
May 22, 2026 - 11:21 CEST