[Cockpit]-[fr-par] - memory pressure on product-frontend

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 3h 21m it lasted.

  Anything that failed between 2026-06-24 11:47 UTC and 2026-06-24 15:08 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. monitoringJun 24, 2026, 11:47 AM UTC

   Between 11:50 a.m. and 1:30 p.m., metrics ingestion on FR-PAR was affected due to an operation performed on one of the components to improve its resilience. Metrics and log data are also affected.

   provider

2. monitoringJun 24, 2026, 12:50 PM UTC

   We are continuing to monitor for any further issues.

   provider

3. identifiedJun 24, 2026, 12:52 PM UTC

   The issue has been identified and a fix is being implemented.

   provider

4. resolvedJun 24, 2026, 3:08 PM UTC

   Following a component overload in Cockpit during an upgrade designed to improve its resilience, difficulties integrating logs and metrics arose from Scaleway products between 11.30 am and 3.30 pm. There may have been a partial loss of this data.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.