- Level
- confirmed
- Worst impact
- Degraded
- Components
- fr-par-1, fr-par-2, fr-par-3, nl-ams-1, nl-ams-2, nl-ams-3, pl-waw-1, pl-waw-2, pl-waw-3, Serverless Functions
- Down Index
- 22of 100
What to do
Check whether you use Scaleway fr-par-1, fr-par-2, fr-par-3, nl-ams-1 and 6 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 1h 44m it lasted.
Anything that failed between 2026-04-28 12:06 UTC and 2026-04-28 13:50 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 4
- investigating
Customers may experience DNS resolution failures for their Serverless Functions in the nl-ams and pl-waw regions, due to an error that happened during the scheduled maintenance: https://status.scaleway.com/incidents/qhh06fhhn47r. Errors for clients might look like: "lookup [...] on 10.32.15.25:53: read udp 100.96.xx.xx:xx->10.32.15.25:53: i/o timeout". We have identified the root cause. Sorry about any inconvenience.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
After investigation, this also affects functions created on new namespaces on fr-par.
provider
- resolved
The root cause has been fixed: all functions now have a working DNS again. The incident is now closed. Impacted functions were: - on fr-par, only functions not attached to a private network, that belong to a namespace created after 2026-04-28 8:00 AM UTC, until 1:05 PM UTC. - on nl-ams, all functions not attached to a private network, between 8:41 AM UTC and 1:46 PM UTC - on pl-waw, all functions not attached to a private network, between 9:30 AM UTC and 1:05 PM UTC The incident on nl-ams and pl-waw is related to the scheduled maintenance https://status.scaleway.com/incidents/zrhfpqjvjyrl. A mismatch between DNS service IPs caused the issue. We deeply apologize for the inconvenience.
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-ddeaf40796
Is Scaleway still down?
No, this incident was resolved 2026-04-28 13:50 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
1h 44m, from 2026-04-28 12:06 UTC to 2026-04-28 13:50 UTC, by the times Scaleway posted.
What was affected?
Scaleway named fr-par-1, fr-par-2, fr-par-3, nl-ams-1 and 6 more.
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.