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

What to do

• Check whether you use Scaleway nl-ams-1, nl-ams-2, nl-ams-3, pl-waw-1 and 3 more. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-03-27 09:57 UTC and 2026-03-27 09:57 UTC may need a replay.

• Subscribe to Scaleway's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=scaleway works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Scaleway 1

1. resolvedMar 27, 2026, 9: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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.