- Level
- confirmed
- Worst impact
- Degraded
- Components
- Domains
- Down Index
- 23of 100
What to do
Check whether you use Scaleway 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 10d 21h it lasted.
Anything that failed between 2026-10-11 10:10 UTC and 2026-10-22 07:23 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 3
- investigating
Several reports of inconsistencies in the zones between our DNS servers s0.dom.scw.cloud and s1.dom.scw.cloud
provider
- monitoring
Updates had piled up, causing these issues. It has now been resolved.
provider
- resolved
The global incident is now solved. If you still experience issues, please reach out our support through usual means.
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-8e4b659466
Is Scaleway still down?
No, this incident was resolved 2026-10-22 07:23 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
10d 21h, from 2026-10-11 10:10 UTC to 2026-10-22 07:23 UTC, by the times Scaleway posted.
What was affected?
Scaleway named 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.