- Level
- confirmed
- Worst impact
- Degraded
- Components
- fr-par-1, Block Storage
- Down Index
- 31of 100
What to do
Check whether you use Scaleway fr-par-1, Block Storage. 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 4h 6m it lasted.
Anything that failed between 2026-11-07 07:22 UTC and 2026-11-07 11:28 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
- identified
Since 22h UTC, mean write latencies slowly increased on one Block cluster on fr-par-1 due to background operations pilling up overnight until 05h19 UTC. Latencies are not increasing anymore and the cluster is processing the remaining operations. The Block Storage team is working to speed up the processing of the remaining tasks. Write latencies are expected to return to normal in a few hours
provider
- resolved
Writes latencies returned to normal levels for this cluster.
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-d399b744ed
Is Scaleway still down?
No, this incident was resolved 2026-11-07 11:28 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
4h 6m, from 2026-11-07 07:22 UTC to 2026-11-07 11:28 UTC, by the times Scaleway posted.
What was affected?
Scaleway named fr-par-1, Block Storage.
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.