Skip to main content
Scaleway

[fr-par] Site-to-site VPN configuration issue

Degraded Lasted 38d 21h · started · Scaleway's page

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

What to do

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

    Anything that failed between 2026-08-20 16:06 UTC and 2026-09-28 13:45 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

    Following a configuration issue during a deployment, numerous routes stopped being advertised, which may have impacted routing to the PAR VPN gateways.

    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-35a2277883

Is Scaleway still down?

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

How long did it last?

38d 21h, from 2026-08-20 16:06 UTC to 2026-09-28 13:45 UTC, by the times Scaleway posted.

What was affected?

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

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.