Struck in red is what Scaleway removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
ChangedStatus#1
Before: monitoring
After: resolved
AddedResolved time#2
Before: not present
After: 2026-11-05 15:52 UTC
AddedUpdateresolved#3
Before: not present
After: Incident is resolved now.
Impacts for users were limited to nl-ams region, and Serverless Containers product:
- From 10:00 UTC to 11:05 UTC: users received HTTP 5xx errors while calling their containers
- From 10:00 UTC to 12:00 UTC: some containers were stuck in creating/updating
- From 09:20 UTC to 12:20 UTC: some containers with VPC support lost connectivity to resources in their PN
These were all unexpected impacts of the following maintenance: https://status.scaleway.com/incidents/f7lpf0j1c2sq. The upgrade was partially applied, since we stopped it to stabilize the situation. While the situation is stable now, some work will still need to be done to fully complete the maintenance in the future, but we will postpone it for now.
In more details: a faulty step during our maintenance caused 1) our gateways to misbehave and start returning HTTP 503 errors and 2) VPC attached containers to be detached from their PN. The situation quickly snowballed, as a lot of pressure was made on the infrastructure, causing other unrelated issues (e.g. containers stuck in creating/updating statuses).
Despite our care, and successful upgrades on other regions (e.g. https://status.scaleway.com/incidents/tf28nvnckksz), the issue arose there because of nl-ams region being more crowded. We will perform additional tests before continuing the maintenance.
We deeply apologize for the inconvenience caused.
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.