Scaleway: [Serverless Functions/Containers] Custom domain can end up in error status after updating a function/container
Timeline of updates
- resolved
A fix has been deployed and domains wrongfully set in "error" status have been updated to "ready" status. As noted before, there was no impact on the domain behavior itself, which continued to redirect requests to the users functions/containers. Now, the status of the domain as returned by the API reflects the real status. Sorry about 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: none) posted by Scaleway, started 2024-02-22 14:47 UTC, resolved after 25 h, 1 update(s).
- Title
- [Serverless Functions/Containers] Custom domain can end up in error status after updating a function/container
- Vendor
- Scaleway
- Date
- URL
- https://rewindex.com/company/scaleway/incidents/1zw7xzs0flzh
Scaleway profileRecent Scaleway incidentsAll outages on February 22, 2024Scaleway in February 2024MarkdownJSON