Skip to main content
Scaleway

[COCKPIT] - [fr-par/pl-waw] - Scaleway Metrics/Logs ingestion down

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

Level
confirmed
Worst impact
Degraded
Components
Cockpit
Down Index
23of 100

What to do

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

    Anything that failed between 2026-06-30 08:23 UTC and 2026-07-08 12:20 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 4

  1. monitoring

    Cockpit impacted this night betwen 1am30 and 8am30 with data loss for all Products metrics and logs on FR-PAR & PL-WAW Regions Root cause : based on last week Cockpit ingestion solution, a high RAM consumption saturated nodes and corrupted replay solution. Status : Cockpit fixed at 8am30 and fix in development to avoid replay corruption on OOM events

    provider

  2. monitoring

    Root cause was finally identified yesterday evening, we make an evolution on staging environments and monitored its behavior today. We plan to deploy this fix next monday morning. Metrics & Logs acquisition are fine since yesterday with a scaling workaround, we keep this solution for the week-end to not impact production on a friday afternoon.

    provider

  3. monitoring

    We applied and monitored today the last fix for high RAM consumption. All seems fine now on Cockpit performances for all regions.

    provider

  4. 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-0dce01aa1f

Is Scaleway still down?

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

How long did it last?

8d 3h, from 2026-06-30 08:23 UTC to 2026-07-08 12:20 UTC, by the times Scaleway posted.

What was affected?

Scaleway named Cockpit.

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.