Status impact color legend
- Black impact: None
- Yellow impact: Minor
- Red impact: Major
- Blue impact: Maintenance
[SERVERLESS CONTAINER][WAW][AMS] Serverless Containers were autonomously redeployed by the platform
Incident
Report for Scaleway
Resolved
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.
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.
This incident affected: Elements - AZ (nl-ams-1, nl-ams-2, nl-ams-3, pl-waw-1, pl-waw-2, pl-waw-3) and Elements - Products (Serverless Container).