Scaleway Outage History

Scaleway experienced a payment result handling issue where customers who paid by card saw their invoices incorrectly displayed as "unpaid" despite successful payment processing. The issue affected the Billing API and caused display inconsistencies for card payments. The incident was resolved after approximately 25 days of investigation and fixes.

Scaleway's Cockpit service experienced disrupted SMTP communication with TEM due to a key rotation issue, preventing the delivery of alert emails. The incident lasted approximately 7 days before being resolved on April 8th, 2026.

Scaleway's webmail service became inaccessible for customers hosted on the pf-012.whm.fr-par.scw.cloud platform in the Paris region. The outage prevented users from accessing their email through the web interface for over 7 days. The issue was resolved on April 8th after implementing a fix and monitoring period.

Four disks failed on Scaleway's SAN cluster server between 23:45 and 01:30 on Sunday, compromising the RAID configuration and affecting SAN services. The team attempted data recovery using a spare server and rebuilt the RAID array over a 75-hour period. The issue was resolved after the RAID rebuild completed successfully.

IPv6 connectivity was unavailable on Scaleway's pf-012.whm.fr-par.scw.cloud platform in the fr-par-2 region, affecting services that rely on IPv6 addresses. The issue was identified and resolved within 19 minutes.

IPv6 connectivity was unavailable on Scaleway's WebHosting Elements platform pf-012.whm.fr-par.scw.cloud in the fr-par-2 region, affecting services that rely on IPv6 addresses. The incident lasted 4.4 hours, with the cause identified after 3.5 hours of investigation before being fully resolved.

Scaleway's Data Warehouse service in the fr-par region experienced issues preventing new deployments from being created, with existing deployment startups also failing intermittently. The incident affected both fr-par-1 and fr-par-2 availability zones for approximately 1.5 hours before being resolved.

Scaleway's Audit Trail API in the fr-par region experienced a partial outage lasting over 10 days, causing customers to receive 503 error responses on some API requests. While API access was impacted, no audit trail events were lost during the incident. The issue was mitigated on March 26th and fully resolved on April 6th after root cause investigation.

Scaleway's MongoDB service in the fr-par-1 region experienced a 21.2-hour connectivity outage where public endpoint IPs were not properly routing to new database nodes. Customers were unable to connect to their MongoDB instances through public endpoints during this period. The issue was resolved by implementing a fix to correct the IP routing configuration.

The NATS stream in Scaleway's PL-WAW region became unresponsive, preventing events from being displayed in the Audit Trail for 40 minutes starting at 9:53 GMT+1. The incident affected the pl-waw-1 component but events were preserved through a backup solution. The issue was resolved at 11:22 a.m. CET with no data loss.