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

What to do

• Check whether you use Scaleway nl-ams-1, nl-ams-2, nl-ams-3, pl-waw-1 and 4 more. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-03-17 17:18 UTC and 2026-03-17 17:18 UTC may need a replay.

• Subscribe to Scaleway's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=scaleway works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Scaleway 1

1. resolvedMar 17, 2026, 5:18 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.