- Level
- confirmed
- Worst impact
- Degraded
- Components
- nl-ams-1, nl-ams-2, nl-ams-3, Serverless Container, Serverless Functions
- Down Index
- 22of 100
What to do
Check whether you use Scaleway nl-ams-1, nl-ams-2, nl-ams-3, Serverless Container and 1 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 4h 29m it lasted.
Anything that failed between 2026-11-05 11:22 UTC and 2026-11-05 15:52 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 6
- identified
The scheduled maintenance https://status.scaleway.com/incidents/f7lpf0j1c2sq did not go as planned. Since 09:50 UTC, Serverless Containers services might have faced connectivity issues. Create and update operations were impacted as well.
provider
- identified
Serverless Container, Serverless Functions are impacted.
provider
- identified
Connectivity has been back to normal since 11:06 UTC. We are continuing to monitor the situation. We are still working on restoring create and update operations, which remain impacted.
provider
- identified
As of 12:00 UTC, containers shouldn't be stuck anymore in "creating" or "updating" status for an abnormal duration. Some containers with VPC support might have lost connectivity to resources inside the Private Network. A redeployment of the container triggered by users could help solving the situation, but we are investigating. Sorry again for any inconvenience.
provider
- monitoring
VPC connectivity issues are now stabilized. Unlike stated previously, only Serverless Containers product is impacted. We are now monitoring the situation. Thanks for your understanding.
provider
- resolved
Incident is resolved now. Impacts for users were limited to nl-ams region, and Serverless Containers product: - From 10:00 UTC to 11:05 UTC: users received HTTP 5xx errors while calling their containers - From 10:00 UTC to 12:00 UTC: some containers were stuck in creating/updating - From 09:20 UTC to 12:20 UTC: some containers with VPC support lost connectivity to resources in their PN These were all unexpected impacts of the following maintenance: https://status.scaleway.com/incidents/f7lpf0j1c2sq. The upgrade was partially applied, since we stopped it to stabilize the situation. While the situation is stable now, some work will still need to be done to fully complete the maintenance in the future, but we will postpone it for now. In more details: a faulty step during our maintenance caused 1) our gateways to misbehave and start returning HTTP 503 errors and 2) VPC attached containers to be detached from their PN. The situation quickly snowballed, as a lot of pressure was made on the infrastructure, causing other unrelated issues (e.g. containers stuck in creating/updating statuses). Despite our care, and successful upgrades on other regions (e.g. https://status.scaleway.com/incidents/tf28nvnckksz), the issue arose there because of nl-ams region being more crowded. We will perform additional tests before continuing the maintenance. We deeply apologize for the inconvenience caused.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-77be248306
Is Scaleway still down?
No, this incident was resolved 2026-11-05 15:52 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
4h 29m, from 2026-11-05 11:22 UTC to 2026-11-05 15:52 UTC, by the times Scaleway posted.
What was affected?
Scaleway named nl-ams-1, nl-ams-2, nl-ams-3, Serverless Container and 1 more.
What caused it?
Scaleway hasn't published a root cause. If it does, it shows here.
Where does this come from?
Scaleway's official status page, https://status.scaleway.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.