Scaleway incident
[Serverless Functions] - [fr-par/nl-ams/pl-waw] DNS resolution failures for all functions
Resolved after 1 hour 43 minutes, affecting fr-par-1 and fr-par-2 and 1 more, on April 28, 2026.
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.
Affected components
Update timeline
- investigating Apr 28, 2026, 12:06 PM UTC
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.
- investigating Apr 28, 2026, 12:11 PM UTC
We are continuing to investigate this issue.
- investigating Apr 28, 2026, 12:16 PM UTC
After investigation, this also affects functions created on new namespaces on fr-par.
- resolved Apr 28, 2026, 01:50 PM UTC
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.
Your product runs on more than Scaleway
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services