- Level
- confirmed
- Worst impact
- Operational
- Components
- Domains, Domains
What to do
Check whether you use Scaleway Domains, Domains. 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 13m it lasted.
Anything that failed between 2026-11-09 16:49 UTC and 2026-11-09 17:02 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 2
- investigating
We are experiencing a DNS resolution issue affecting the following nameservers over IPv4 only : ns0.online.net and ns0.dom.scw.cloud.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-c238fa843f
Is Scaleway still down?
No, this incident was resolved 2026-11-09 17:02 UTC. For Scaleway's live state, see https://down.guide/providers/scaleway.
How long did it last?
13m, from 2026-11-09 16:49 UTC to 2026-11-09 17:02 UTC, by the times Scaleway posted.
What was affected?
Scaleway named Domains, Domains.
What caused it?
Scaleway hasn't published a root cause. If it does, it shows here.
Where does this come from?
Scaleway's official status page, https://status.scaleway.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.