Scaleway: [Serverless Containers] - [nl-ams] spurious 403 errors
Timeline of updates
- resolved
Incident has now been resolved. Between 2025-10-22 08:17 UTC and 2025-10-23 09:10 UTC, around 20% of users on the nl-ams region might have received spurious 403 errors while calling their function or container endpoint. The root cause was a misconfiguration on one of our system components. This has been fixed, and we took preventive measures to avoid this kind of errors to happen again in the future. We deeply apologize for any inconvenience. Thanks for your understanding.
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 2025-10-23 08:56 UTC, resolved after 3.3 h, 1 update(s).
- Title
- [Serverless Containers] - [nl-ams] spurious 403 errors
- Vendor
- Scaleway
- Date
- URL
- https://rewindex.com/company/scaleway/incidents/f46rqnh4864c
Scaleway profileRecent Scaleway incidentsAll outages on October 23, 2025Scaleway in October 2025MarkdownJSON