Skip to main content
Scaleway

[LOAD BALANCER] - [PAR1] - Monitoring PN down leading to autohealing mechanism stopped

Degraded Monitoring a fix since · started · Scaleway's page

Updates every minute from the provider's page.

Level
confirmed
Worst impact
Degraded
Components
fr-par-1, Load Balancer
Down Index
33of 100

Summary

Scaleway says Load Balancer creation and configuration, and auto-healing, in PAR1 were affected by an internal metadata API failure, starting 2026-11-03 at 09:54 UTC. The incident is now in monitoring, and the provider says the situation should be back to normal.

Written by anthropic/claude-haiku-5.5 from Scaleway's own updates.

What to do

  • Check whether you use Scaleway fr-par-1, Load Balancer. 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.
  • Scaleway says a fix is out: check your own error rates before you undo any failover.

  • Watch Scaleway's own updates; this page re-reads them every minute.

  • 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 4

  1. investigating

    Issues with LB creation/configuration and auto-healing in PAR1 due to internal metadata API failure

    provider

  2. investigating

    We are continuing to investigate this issue.

    provider

  3. investigating

    We are continuing to investigate this issue.

    provider

  4. monitoring

    The situation should be back to normal

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

Is Scaleway down right now?

Scaleway reports degraded ([LOAD BALANCER] - [PAR1] - Monitoring PN down leading to autohealing mechanism stopped), open since 2026-11-03 09:54 UTC; it says a fix is out and it is monitoring. Live state for every component: https://down.guide/scaleway.

What was affected?

Scaleway named fr-par-1, Load Balancer.

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.