Status impact color legend
- Black impact: None
- Yellow impact: Minor
- Red impact: Major
- Blue impact: Maintenance
[VPC][AMS][WAW] DNS Resolution Incident in Isolated Kapsule Clusters (VPC)
Incident
Report for Scaleway
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.
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.
This incident affected: Elements - AZ (nl-ams-1, nl-ams-2, nl-ams-3, pl-waw-1, pl-waw-2, pl-waw-3) and Elements - Products (Private Network, Kubernetes Kapsule).