Skip to main content
Scaleway

[FR-PAR] Network perturbations

Degraded Lasted 6d 18h · started · Scaleway's page

Level
confirmed
Worst impact
Degraded
Components
fr-par-1, fr-par-2, fr-par-3
Down Index
24of 100

What to do

  • Check whether you use Scaleway fr-par-1, fr-par-2, fr-par-3. 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 6d 18h it lasted.

    Anything that failed between 2026-09-29 13:44 UTC and 2026-10-06 08:21 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

  1. monitoring

    We have observed local perturbations on the backbone network of FR-PAR region, fixes have been deployed, we are monitoring the situation

    provider

  2. 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-aa4d3f52f3

Is Scaleway still down?

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

How long did it last?

6d 18h, from 2026-09-29 13:44 UTC to 2026-10-06 08:21 UTC, by the times Scaleway posted.

What was affected?

Scaleway named fr-par-1, fr-par-2, fr-par-3.

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.