Skip to main content
Scaleway

san-dc2-7 unreachable

Degraded Lasted 3d 17h · started · Scaleway's page

Level
confirmed
Worst impact
Degraded
Components
SAN

What to do

  • Check whether you use Scaleway SAN. 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 3d 17h it lasted.

    Anything that failed between 2026-09-18 13:45 UTC and 2026-09-22 07: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

    A hardware issue impacted a RPN node (dc2-7) from 17/09/26 12h11 UTC to 18/09/26 13h01. The service is now up for the clients using this node We are monitoring closely for any new issues on the node and may need another downtime if the hardware issue persist.

    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-d54ea8a0aa

Is Scaleway still down?

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

How long did it last?

3d 17h, from 2026-09-18 13:45 UTC to 2026-09-22 07:21 UTC, by the times Scaleway posted.

What was affected?

Scaleway named SAN.

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.