Scaleway incident

[SERVERLESS CONTAINER][WAW][AMS] Serverless Containers were autonomously redeployed by the platform

Notice Resolved View vendor source →

Scaleway experienced a notice incident on March 27, 2026 affecting nl-ams-1 and nl-ams-2 and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.

Started
Mar 27, 2026, 09:57 AM UTC
Resolved
Mar 27, 2026, 09:57 AM UTC
Duration
Detected by Pingoru
Mar 27, 2026, 09:57 AM UTC

Affected components

nl-ams-1nl-ams-2nl-ams-3pl-waw-1pl-waw-2pl-waw-3Serverless Container

Update timeline

  1. resolved Mar 27, 2026, 09:57 AM UTC

    On March 26, 2026, we experienced an incident affecting Serverless Containers in the following regions: pl-waw: from approximately 11:30 CET to 11:36 CET nl-ams: from approximately 13:30 CET to 13:40 CET During these periods, a platform-level component triggered an automatic redeployment of active Serverless Containers. This action was initiated without any user intervention and was unintended. The sudden scaling activity caused temporary disruptions across the Serverless platform, including brief network connectivity issues—particularly for containers connected to VPC. Impact: - Brief service interruptions for running Serverless Containers - Transient network issues, especially for Serverless Containers configured with private networks - Increased startup latency during the redeployment window All systems are now operating normally, and no further action is required from users. We sincerely apologize for the disruption. Our team has identified the cause. No reoccurrence is expected to happen. We appreciate your understanding and patience.