Skip to main content
Scaleway

[EDGE] - 503 error

Degraded Lasted 6d 7h · started · Scaleway's page

Level
confirmed
Worst impact
Degraded
Components
Edge service
Down Index
23of 100

What to do

  • Check whether you use Scaleway Edge service. 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 6d 7h it lasted.

    Anything that failed between 2026-08-12 08:00 UTC and 2026-08-18 15:41 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 3

  1. investigating

    Customer may experience 503 errors on edge service.

    provider

  2. identified

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

    provider

  3. 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-132e1544fd

Is Scaleway still down?

No, this incident was resolved 2026-08-18 15:41 UTC. For Scaleway's live state, see https://down.guide/scaleway.

How long did it last?

6d 7h, from 2026-08-12 08:00 UTC to 2026-08-18 15:41 UTC, by the times Scaleway posted.

What was affected?

Scaleway named Edge service.

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.