- Level
- confirmed
- Worst impact
- Degraded
- Components
- Kafka
- Down Index
- 19of 100
What to do
Check whether you use Scaleway Kafka. 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 2h 29m it lasted.
Anything that failed between 2026-05-22 09:16 UTC and 2026-05-22 11:45 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
We are currently investigating on that incident.
provider
- investigating
We are continuing to investigate this issue.
provider
- resolved
Following an infrastructure update, the Kafka clusters were no longer reachable via the private network. The issue has been resolved, and the services are operational again.
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-f373fda7e0
Is Scaleway still down?
No, this incident was resolved 2026-05-22 11:45 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
2h 29m, from 2026-05-22 09:16 UTC to 2026-05-22 11:45 UTC, by the times Scaleway posted.
What was affected?
Scaleway named Kafka.
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.