Is Container Registry down?
Container Registry is having issues
Right now
Partly. [Container Registry] Increase in 5xx errors on fr-par Container Registry.
Last checked (2026-10-10 08:11 UTC) from status.scaleway.com · every 180s
For agents
proceed
Proceed, expect slow or flaky responses.
GET upbutler.com/status/scaleway/container-registry/status.agent.json
MCP: upstream_status {"service":"scaleway","component":"container-registry"}
Container Registry is one of the components Scaleway reports on its status page. European cloud: instances, serverless, object storage and generative APIs.
Part of Scaleway status.
What Scaleway says
Degraded· 1 open incident
Taken as is from Scaleway's own status page API. Incident titles and component names below are theirs. Narrowed to what concerns Container Registry.
Open status.scaleway.comWhat UpButler measured
There is no keyless endpoint of Scaleway that says anything useful, so UpButler does not probe it. To check your own Scaleway account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Open at Scaleway for Container Registry
- [Container Registry] Increase in 5xx errors on fr-par Container Registryinvestigating · impact minor
Since · fr-par-1, fr-par-2, fr-par-3, Container Registry, Jobs, Kafka +3
We added other impacted products and we are still investigating.
Text written by Scaleway, shown unchanged.
Container Registry: what Scaleway lists
1 of 1 not operational
Elements - Products
- Container RegistryDegraded
Container Registry incidents, last 90 days
- 2026-07-13: no record
- 2026-07-14: no record
- 2026-07-15: no record
- 2026-07-16: no record
- 2026-07-17: no record
- 2026-07-18: no record
- 2026-07-19: no record
- 2026-07-20: no record
- 2026-07-21: no record
- 2026-07-22: no record
- 2026-07-23: no record
- 2026-07-24: no record
- 2026-07-25: no record
- 2026-07-26: no record
- 2026-07-27: no record
- 2026-07-28: no record
- 2026-07-29: no record
- 2026-07-30: no record
- 2026-07-31: no record
- 2026-08-01: no record
- 2026-08-02: no record
- 2026-08-03: no record
- 2026-08-04: no record
- 2026-08-05: no record
- 2026-08-06: no record
- 2026-08-07: no record
- 2026-08-08: no record
- 2026-08-09: no record
- 2026-08-10: no record
- 2026-08-11: no record
- 2026-08-12: no record
- 2026-08-13: no record
- 2026-08-14: no record
- 2026-08-15: no record
- 2026-08-16: no record
- 2026-08-17: no record
- 2026-08-18: no record
- 2026-08-19: no record
- 2026-08-20: no record
- 2026-08-21: no record
- 2026-08-22: no record
- 2026-08-23: no record
- 2026-08-24: no record
- 2026-08-25: no record
- 2026-08-26: no record
- 2026-08-27: no record
- 2026-08-28: no record
- 2026-08-29: no record
- 2026-08-30: no record
- 2026-08-31: no record
- 2026-09-01: no record
- 2026-09-02: no record
- 2026-09-03: no record
- 2026-09-04: no record
- 2026-09-05: no record
- 2026-09-06: no record
- 2026-09-07: no record
- 2026-09-08: no record
- 2026-09-09: no record
- 2026-09-10: no record
- 2026-09-11: no record
- 2026-09-12: no record
- 2026-09-13: no record
- 2026-09-14: no record
- 2026-09-15: no record
- 2026-09-16: no record
- 2026-09-17: no record
- 2026-09-18: no record
- 2026-09-19: no record
- 2026-09-20: no record
- 2026-09-21: no record
- 2026-09-22: no record
- 2026-09-23: no record
- 2026-09-24: no record
- 2026-09-25: no record
- 2026-09-26: no record
- 2026-09-27: no record
- 2026-09-28: no record
- 2026-09-29: no record
- 2026-09-30: no record
- 2026-10-01: no record
- 2026-10-02: no record
- 2026-10-03: no record
- 2026-10-04: no record
- 2026-10-05: no record
- 2026-10-06: no record
- 2026-10-07: no record
- 2026-10-08: minor incident
- 2026-10-09: minor incident
- 2026-10-10: minor incident
Each bar is a day, coloured by the worst incident Scaleway reported for Container Registry. It is their incident record, not a measurement of uptime.
No finished incidents on record yet since 2026-10-08. UpButler keeps what Scaleway publishes for 90 days from the day it starts tracking a service.
Get alerted when Container Registry goes down
No account. One email when Scaleway reports an incident that affects Container Registry, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.
Or follow the RSS feed. On UpButler? Add Scaleway as a dependency to route it to Slack, Teams or a webhook.
Status badge
Show Container Registry's current status in a README or an internal wiki. It updates by itself.
[](https://upbutler.com/status/scaleway/container-registry)Tell your outage from Scaleway's
Declare that your project depends on Container Registry. When one of your monitors fails while Scaleway has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- service: scaleway
components: ["Container Registry"]curl -s https://upbutler.com/status/scaleway/container-registry/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "scaleway",
"component": {
"slug": "container-registry",
"name": "Container Registry"
},
"verdict": "proceed",
"status": "degraded",
"reason": "[Container Registry] Increase in 5xx errors on fr-par Container Registry",
"retryAfterSec": null,
"incident": {
"title": "[Container Registry] Increase in 5xx errors on fr-par Container Registry",
"url": "https://status.scaleway.com/incidents/plhwpkrc8qqh"
},
"probe": null
}Questions
- Is Container Registry down right now?
- Partly. As of 2026-10-10 08:11 UTC, Container Registry is having issues, with an open incident: "[Container Registry] Increase in 5xx errors on fr-par Container Registry". This page reads the status again every 3 minutes.
- Where does this status come from?
- From Scaleway's own status page API at https://status.scaleway.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Scaleway's words. Their page covers more than this page shows; it is narrowed to the parts that concern Container Registry.
- Can I get an alert when Container Registry goes down?
- Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Scaleway reports an incident that affects Container Registry and one when it is over. There is also an RSS feed at https://upbutler.com/status/scaleway/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
- How can my agent or app check Container Registry status?
- Fetch https://upbutler.com/status/scaleway/container-registry/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"scaleway","component":"container-registry"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Scaleway's?
- Add "scaleway" to the dependencies of your UpButler workspace. When one of your monitors fails while Scaleway has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
Also check
UpButler is not affiliated with Scaleway. Status and incident text belong to Scaleway and are read from their public status source; the probe result is UpButler's own measurement.