- Level
- confirmed
- Worst impact
- Degraded
- Components
- nl-ams-1, nl-ams-2, nl-ams-3, Serverless Functions
- Down Index
- 19of 100
What to do
Check whether you use Scaleway nl-ams-1, nl-ams-2, nl-ams-3, Serverless Functions. 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 1h 4m it lasted.
Anything that failed between 2026-03-05 15:28 UTC and 2026-03-05 16:32 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 3
- investigating
Since 03/02 and the start of this maintenance: https://status.scaleway.com/incidents/p2cj27y80n9w, an understated breaking change was deployed. Now, health checks configured by users are not just used as readiness probes, but liveness probes. As a result, some users containers with failing probes are restarted in loop, even before they have a chance to start correctly. We will disable temporarily this new behavior until we measure the impacts and find a remediation. Sorry about any inconvenience.
provider
- monitoring
We have deployed a fix rolling back the probe change done during the migration. Now, health checks are used as before as only readiness probes, and are not used to restart the containers. We are still monitoring, but containers shouldn't restart anymore because of aggressive probing. We will reintroduce the "liveness probe" feature later (maybe optional), but we will make sure to communicate clearly and measure more thoroughly the impacts. Sorry about any inconvenience.
provider
- resolved
We have finished monitoring the situation. Container instances are now running without a liveness probe, preventing them from restarting. Now, restarts are only triggered by users applicative errors (e.g. if the container crashes). Note that after our fix made earlier, users might have seen their container waken up, due to the deployed change. Sorry again for the inconvenience.
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-5651681772
Is Scaleway still down?
No, this incident was resolved 2026-03-05 16:32 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
1h 4m, from 2026-03-05 15:28 UTC to 2026-03-05 16:32 UTC, by the times Scaleway posted.
What was affected?
Scaleway named nl-ams-1, nl-ams-2, nl-ams-3, Serverless Functions.
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.