Scaleway: [VPC][AMS][WAW] DNS Resolution Incident in Isolated Kapsule Clusters
Timeline of updates
- resolved
Summary: Following a deployment to release VPC Peering in public beta, a change in DNS resolution within VPC caused DNS issues. These issues only affected Kapsule clusters in full isolation mode using Debian 12/13 containers and were limited to the nl-ams and pl-waw regions. Timeline: 09:39 UTC — Incident began after the VPC Peering deployment. 11:30 UTC — First rollback completed on nl-ams-1; investigation and reproduction efforts began. ~16:10 UTC — Confirmed the scope was limited to Debian 12/13 containers in full isolation mode. 16:13 UTC — Full rollback completed on nl-ams-2, nl-ams-3, pl-waw-1, pl-waw-2, pl-waw-3. The issue is now resolved. We are continuing to analyze the root cause and will provide a permanent fix.
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 2026-03-17 17:18 UTC, resolved after 0 min, 1 update(s).
- Title
- [VPC][AMS][WAW] DNS Resolution Incident in Isolated Kapsule Clusters
- Vendor
- Scaleway
- Date
- URL
- https://rewindex.com/company/scaleway/incidents/f5chbn540dz5
Scaleway profileRecent Scaleway incidentsAll outages on March 17, 2026Scaleway in March 2026MarkdownJSON