# \[VPC\]\[AMS\]\[WAW\] DNS Resolution Incident in Isolated Kapsule Clusters

- Provider: [Scaleway](https://down.guide/scaleway)
- Level: confirmed
- Impact: Degraded
- lasted 0m
- started 2026-03-17 17:18 UTC
- nl-ams-1, nl-ams-2, nl-ams-3 +5
- id: DWN-f9e6ddee76
- Official page: https://stspg.io/rtv9cxsmpk4y

## Updates from Scaleway
### 2026-03-17 17:18 UTC: 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 the builder: does your app depend on Scaleway? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=scaleway) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Scaleway.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-f9e6ddee76), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.