Scaleway: [Serverless Functions/Containers] [nl-ams] 503 errors received by clients calling their functions/containers
Timeline of updates
- resolved
On nl-ams region, between 2025-02-11 10:24 UTC and 2025-02-11 11:47 UTC, users might have received 503 errors (upstream connection termination) when calling their functions/containers: ~1.2% of requests estimated on that time frame, mostly grouped in the first hour: around ~3.6% from 10:24 UTC until 11:00 UTC. The 503 errors root cause is not the same as we experienced in the past; this one is due to unattended restarts of system components. We apologize for any 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 2025-02-11 10:30 UTC, resolved after 0 min, 1 update(s).
- Title
- [Serverless Functions/Containers] [nl-ams] 503 errors received by clients calling their functions/containers
- Vendor
- Scaleway
- Date
- URL
- https://rewindex.com/company/scaleway/incidents/q10ybdkqrb61
Scaleway profileRecent Scaleway incidentsAll outages on February 11, 2025Scaleway in February 2025MarkdownJSON