Scaleway: [Serverless Containers] - [nl-ams] - some containers are restarting because of aggressive probing
Timeline of updates
- 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.
From Scaleway’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.scaleway.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Scaleway, started 2026-03-05 15:28 UTC, resolved after 1.1 h, 1 update(s).
- Title
- [Serverless Containers] - [nl-ams] - some containers are restarting because of aggressive probing
- Vendor
- Scaleway
- Date
- URL
- https://rewindex.com/company/scaleway/incidents/vgc1rrdz3bdp
Scaleway profileRecent Scaleway incidentsAll outages on March 5, 2026Scaleway in March 2026MarkdownJSON