- Level
- confirmed
- Worst impact
- Degraded
- Components
- Observability
- Down Index
- 23of 100
What to do
Check whether you use Scaleway Observability. 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 1d 6h it lasted.
Anything that failed between 2026-06-30 05:42 UTC and 2026-07-01 12:31 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
- investigating
Customers may experience missing compute metrics on Instance Orchestration due to a failure on an internal component.
provider
- resolved
The incident is fully solved since around 7h30 UTC on 2026-06-30. It was a side-effect of https://status.scaleway.com/incidents/0vtzpl5bklrh where cockpit metrics were lost on fr-par/pl-waw. There should have been no impact on your infrastructure.
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-46dd8f5c02
Is Scaleway still down?
No, this incident was resolved 2026-07-01 12:31 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
1d 6h, from 2026-06-30 05:42 UTC to 2026-07-01 12:31 UTC, by the times Scaleway posted.
What was affected?
Scaleway named Observability.
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.