Scaleway Outage History

Scaleway's fr-par-2 region experienced a complete depletion of public IPv4 addresses, preventing users from creating new instances that required IPv4 connectivity. The IPv4 shortage affected the Instance Orchestration service and lasted 18 minutes before being resolved.

Scaleway's Cockpit monitoring service experienced data ingestion and query latencies in the PL-WAW region for 23.9 hours. The latency issues affected the performance of the cockpit dashboard and monitoring capabilities in that region. The incident was resolved after the team implemented a solution.

Scaleway's S3 pipeline experienced 502 errors occurring on cache misses, affecting edge services globally for nearly 98 hours. The incident was classified as minor severity and has been resolved.

Scaleway's DNS Management for Elements experienced a partial outage causing intermittent service failures, primarily affecting access between 4am and 7am. The incident impacted the Domains component and lasted approximately 4.3 hours before being fully resolved.

Scaleway's email gateway experienced a 22.4-hour outage that prevented users with Microsoft email domains (outlook.fr, hotmail, live, etc.) from receiving authentication codes and transactional emails. The incident affected email delivery specifically to Microsoft-hosted email services. The issue was resolved on February 26th, 2026 at 09:35 CET.

Scaleway's Container Registry in the Paris region (fr-par) experienced high rates of image pull and push failures starting at 09:30, impacting users' ability to interact with container images. The incident affected the fr-par-1 and fr-par-2 components and lasted approximately 211 hours before being resolved. The service has since returned to normal operation.

Several Load Balancers in Scaleway's pl-waw-2 region experienced downtime, impacting the availability of services that relied on these load balancers. The incident affected the LBaaS (Load Balancer as a Service) component and lasted approximately 3.9 hours before being resolved.

A network outage in Scaleway's PL-WAW region between 8:45 and 9:00 UTC caused multiple RDB database clusters to failover, resulting in brief interruptions to database services. The incident affected the pl-waw-1 availability zone and DBaaS components for approximately 6 minutes. The issue was resolved through the automatic cluster failover process.

Scaleway experienced increased latencies for API requests in the PL-WAW region, affecting the Account API, Billing API, and pl-waw-1 component. The latency issues impacted application performance for users relying on API Gateway services. The incident was resolved after 17 minutes of investigation and remediation.

Scaleway's Cockpit service experienced a resource usage ingestion issue that caused delays in data processing and resulted in slightly inaccurate monthly resource usage reporting. The incident lasted approximately 41 days, during which users may have seen incorrect usage metrics. A fix was implemented and monitored until the issue was fully resolved.