Scaleway incident

FR-PAR-2 connectivity loss

Critical Ongoing View vendor source →

Scaleway is currently experiencing a critical incident affecting Dedibox and fr-par-1 and 1 more component, which began 13h ago. The vendor's full update timeline is below.

Started
May 22, 2026, 09:21 AM UTC
Resolved
Ongoing
Duration
● 13h 25m
Detected by Pingoru
May 22, 2026, 09:21 AM UTC

Affected components

Dediboxfr-par-1fr-par-2fr-par-3DC5

Update timeline

  1. investigating May 22, 2026, 09:21 AM UTC

    We are currently investigating on that issue right now.

  2. investigating May 22, 2026, 09:21 AM UTC

    We are continuing to investigate this issue.

  3. investigating May 22, 2026, 09:23 AM UTC

    We are continuing to investigate this issue.

  4. monitoring May 22, 2026, 09:42 AM UTC

    Most services recovered and our teams are mobilized to recover the rest. Root cause is a power issue in datacenter.

  5. monitoring May 22, 2026, 10:24 AM UTC

    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.”

  6. monitoring May 22, 2026, 10:28 AM UTC

    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

  7. identified May 22, 2026, 10:31 AM UTC

    Datacenter informs us that we are running on power generators for now until the root cause is identified

  8. identified May 22, 2026, 10:44 AM UTC

    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.

  9. monitoring May 22, 2026, 11:10 AM UTC

    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

  10. monitoring May 22, 2026, 11:25 AM UTC

    Clarification: only network rooms are running on power generators, with enough fuel for a few days

  11. monitoring May 22, 2026, 12:26 PM UTC

    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

  12. monitoring May 22, 2026, 02:30 PM UTC

    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

  13. monitoring May 22, 2026, 02:57 PM UTC

    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.

  14. monitoring May 22, 2026, 08:30 PM UTC

    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