Skip to main content
Scaleway

[OBJS] - [PAR] - Lifecycle Job Execution

Degraded Lasted 33d 22h · started · Scaleway's page

Level
confirmed
Worst impact
Degraded
Components
Object Storage
Down Index
23of 100

What to do

  • Check whether you use Scaleway Object 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 33d 22h it lasted.

    Anything that failed between 2026-03-05 11:01 UTC and 2026-04-08 09:02 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. identified

    Since 03/03/26, daily Lifecycle jobs have failed to execute for some buckets. Status: Root cause identified; fix ready for deployment. Action: Once deployed, jobs will run immediately to clear the backlog.

    provider

  2. monitoring

    A fix has been implemented and we are monitoring the results.

    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-6c78c3b16c

Is Scaleway still down?

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

How long did it last?

33d 22h, from 2026-03-05 11:01 UTC to 2026-04-08 09:02 UTC, by the times Scaleway posted.

What was affected?

Scaleway named Object 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.