Skip to main content
Scaleway

[Edge Services] - [world] High amount of 503 on pipeline with Object storage backend

Degraded Lasted 0m · started · Scaleway's page

Level
confirmed
Worst impact
Degraded
Regions
eu
Down Index
12of 100

What to do

  • Check whether you use Scaleway 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 0m it lasted.

    Anything that failed between 2026-07-09 09:29 UTC and 2026-07-09 07:00 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 1

  1. resolved

    Today, between 9:12 AM and 10:15 AM (Paris time), customers experienced a high number of HTTP 503 errors on Edge Services pipelines with Object Storage backends due to DNS resolution issues affecting an internal component. This incident has now been resolved, and our teams are continuing to monitor the situation.

    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-1c24f69a7f

Is Scaleway still down?

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

How long did it last?

0m, from 2026-07-09 09:29 UTC to 2026-07-09 07:00 UTC, by the times Scaleway posted.

What was affected?

Scaleway named 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.