Skip to main content
Scaleway

- DC3 - 500 errors on Dedibackup

Degraded Lasted 1h 56m · started · Scaleway's page

Level
confirmed
Worst impact
Degraded
Components
Dedibackup

What to do

  • Check whether you use Scaleway Dedibackup. 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 56m it lasted.

    Anything that failed between 2026-04-08 11:24 UTC and 2026-04-08 13:20 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

  1. investigating

    Some customers may experience 500 errors when trying to connect to Dedibackup in DC3.

    provider

  2. identified

    Some customers may experience 500 errors when trying to connect to Dedibackup in fr-par-1.

    provider

  3. 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-dedf7c1f38

Is Scaleway still down?

No, this incident was resolved 2026-04-08 13:20 UTC. For Scaleway's live state, see https://down.guide/scaleway.

How long did it last?

1h 56m, from 2026-04-08 11:24 UTC to 2026-04-08 13:20 UTC, by the times Scaleway posted.

What was affected?

Scaleway named Dedibackup.

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.