ChangesScaleway[NL-AMS] - [Serverless Containers] - 20% of client requests failed with HTTP 503 errors
Scaleway: Incident silently edited: [NL-AMS] - [Serverless Containers] - 20% of client requests failed with HTTP 503 errors
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what Scaleway removed; blue is what they added. Muted text is unchanged context.
Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
Before captured
In the 2026-10-29 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
5d0adac67ef94181…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
History of this incident
TodayMonday, November 2Mon, Nov 2
1 rewrite
- EditedEdited by the vendor
[NL-AMS] - [Serverless Containers] - 20% of client requests failed with HTTP 503 errorsthis change
Thursday, October 29
2 rewrites
- Wording onlyEdited by the vendor
[NL-AMS] - 20% of client requests failed with HTTP 503 errors
Scaleway removed “[CAAS]” from the incident title, leaving “[NL-AMS] - 20% of client requests failed with HTTP 503 errors”; the edit changes only the title, not the stated impact.
- Minor editEdited by the vendor
[CAAS] - [NL-AMS] - 20% of client requests failed with HTTP 503 errors
Scaleway changed the recorded impact level of the [CAAS] - [NL-AMS] incident from none to minor; the incident title reports that 20% of client requests failed with HTTP 503 errors. The edit provides no start time, duration, cause or fix.