- Level
- confirmed
- Worst impact
- Degraded
- Components
- Databases
- Down Index
- 16of 100
What to do
Check whether you use Scaleway Databases. 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 37m it lasted.
Anything that failed between 2026-03-24 13:55 UTC and 2026-03-24 14:32 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 currently experiencing an issue with DNS resolution for entries related to the Private Network, which is affecting MongoDB SRV record lookups. This is preventing some customers from connecting to their MongoDB instances when using Private Network endpoints. Our engineering teams are actively investigating and working to resolve the issue as quickly as possible. We sincerely apologise for the inconvenience and will share updates as soon as more information becomes available.
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-9b9c7fda83
Is Scaleway still down?
No, this incident was resolved 2026-03-24 14:32 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
37m, from 2026-03-24 13:55 UTC to 2026-03-24 14:32 UTC, by the times Scaleway posted.
What was affected?
Scaleway named Databases.
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.