ChangesScaleway[Managed database] - [AMS] - New instances can't be provisioning
Scaleway: Incident silently edited: [Managed database] - [AMS] - New instances can't be provisioning
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 these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
Before captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
c170b8209d4e4998…After captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
737c8b6d0d779461…
History of this incident
Tuesday, October 27
1 rewrite
- Wording onlyEdited by the vendor
[Managed database] - [AMS] - New instances can't be provisioningthis change
Cite this
Incident silently edited: [Managed database] - [AMS] - New instances can't be provisioning on Scaleway’s status page, changed 2026-10-27 16:54 UTC (change 1 of 1).
- Title
- Incident silently edited: [Managed database] - [AMS] - New instances can't be provisioning
- Vendor
- Scaleway
- Date
- URL
- https://rewindex.com/change/rb6ede4c831ef08