Scaleway Outage History

Scaleway's Cockpit service in the fr-par region experienced elevated 5xx errors that prevented customers from ingesting logs properly. The issue affected log ingestion functionality for approximately 16.2 hours. The incident was resolved after investigation and remediation efforts.

An internal API service issue in Scaleway's it-mil-1 region caused Cloud-init to fail loading the Scaleway datasource, resulting in instances ending up in an unconfigured state. The problem affected the Instances service and prevented proper instance configuration during startup. The incident was resolved after 26 minutes once the culprit was identified and fixed.

Scaleway experienced network connectivity issues affecting customers in DC2 Room 108 Rack A7 due to a configuration error on an internal component. The incident lasted 2.1 hours before being fully resolved with all services returning to normal operation.

Scaleway experienced high latencies on a block storage cluster in the PAR-1 region starting at 13:20 UTC, which impacted multiple database services including MongoDB, PostgreSQL, MySQL, Serverless, Data Warehouse, Cockpit, and ServerlessDB. The block storage issue was corrected after several hours, followed by additional time to manage side effects on dependent services. The incident was fully resolved after 47.3 hours with no data loss detected and all services returned to healthy operation.

Scaleway's Data Warehouse service in the fr-par region experienced issues where newly generated S3 API keys had insufficient bucket permissions, preventing customers from accessing their storage buckets. The incident affected users who created new API keys during the outage period. The service was restored after 1 hour of investigation and remediation.

Scaleway's Instance Orchestration APIs in the pl-waw region experienced failures for 3.9 hours due to an internal component failure during routine deployments. The outage affected customers' ability to use Instance Orchestration APIs and impacted the Instances service component. The issue was identified and resolved, with monitoring implemented to ensure continued stability.

Scaleway's Dedibackup service in DC3 experienced 500 errors that prevented some customers from connecting to the backup service. The incident lasted approximately 2 hours and affected the Dedibackup component in the fr-par-1 region. The issue was identified and resolved without further details on the specific cause or remediation steps.

Scaleway's Container Registry API in the nl-ams region experienced a high error rate for 3.8 hours, causing customers to encounter failures when accessing registry services. The engineering team implemented a fix and monitored the results before confirming full resolution of the incident.

A public switch failure in Scaleway's DC5 data center caused servers in Rack D39 to lose network access and become unreachable, though RPN network connectivity remained available. The incident affected Dedibox services in DC5 for 4.5 hours until the faulty switch was replaced and network connectivity was restored.

Scaleway experienced a minor incident affecting Windows system installations on their Dedibox service, impacting Windows 2019 (Hyper-V, Standard, Datacenter) and Windows 2022 (Standard, Datacenter) variants. The installation process was broken for these Windows operating systems during the incident. The issue was resolved after 6.6 hours of investigation and remediation efforts.