- Level
- confirmed
- Worst impact
- Degraded
- Components
- APIs
- Regions
- eu
- Down Index
- 21of 100
What to do
Check whether you use Scaleway APIs in eu. 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 42m it lasted.
Anything that failed between 2026-07-23 14:41 UTC and 2026-07-23 15:23 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
- identified
Since around 1 PM UTC, some internal connections to Scaleway API on it-mil region started to fail. As a result: -Pushes to rg.it-mil.scw.eu are failing with HTTP 500 -Serverless Containers deployments are failing (resources stuck in creating) -etc. (list is not exhaustive)
provider
- resolved
The situation has been back to normal since 3:15 PM. Pushes to the registry and container deployments in the IT-mil region are working again. Sorry about any inconvenience.
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-6a4c4d63e3
Is Scaleway still down?
No, this incident was resolved 2026-07-23 15:23 UTC. For Scaleway's live state, see https://down.guide/scaleway.
How long did it last?
42m, from 2026-07-23 14:41 UTC to 2026-07-23 15:23 UTC, by the times Scaleway posted.
What was affected?
Scaleway named APIs in eu.
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.