- Level
- confirmed
- Worst impact
- Degraded
- Scaleway says
- 2026-11-09 09:00 to 12:45 UTC (3h 45m)
- Components
- Cockpit
- Down Index
- 32of 100
Summary
Scaleway says some users in fr-par may have had errors accessing Cockpit Grafana from 11:00 to 14:45 CEST. The provider says the problem is now fixed, the incident is in monitoring, and it is under investigation.
Written by anthropic/claude-haiku-5.5 from Scaleway's own updates.
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 20h 56m it lasted.
Anything that failed between 2026-11-09 13:59 UTC and 2026-11-10 10:55 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
- monitoring
From 11:00 CEST to 14:45 CEST Some users may have experienced errors when accessing their cockpit. The problem is now fixed and under investigation
provider
- 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-fe153b35b0
Is Scaleway still down?
No, this incident was resolved 2026-11-10 10:55 UTC. For Scaleway's live state, see https://down.guide/providers/scaleway.
How long did it last?
20h 56m, from 2026-11-09 13:59 UTC to 2026-11-10 10:55 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.