Skip to main content
Scaleway

[NL-AMS] - [Serverless Containers] - 20% of client requests failed with HTTP 503 errors

Degraded Lasted 0m · started · Scaleway's page

Level
confirmed
Worst impact
Degraded
Components
Serverless Container
Down Index
8of 100

What to do

  • Check whether you use Scaleway Serverless Container. 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-10-29 13:28 UTC and 2026-10-29 13:28 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

    October 28, 2026 – 16:14 to 16:27 UTC Approximately 20% of Serverless Containers requests in nl-ams returned HTTP 503 errors, and some active client connections may have been interrupted.

    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-bdbd88cc78

Is Scaleway still down?

No, this incident was resolved 2026-10-29 13:28 UTC. For Scaleway's live state, see https://down.guide/scaleway.

How long did it last?

0m, from 2026-10-29 13:28 UTC to 2026-10-29 13:28 UTC, by the times Scaleway posted.

What was affected?

Scaleway named Serverless Container.

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.