Is Scaleway down?
Scaleway is having issues
Right now
Partly. [Support] Delays in ticket processing.
Last checked (2026-10-10 07:16 UTC) from status.scaleway.com · every 180s
For agents
proceed
Proceed, expect slow or flaky responses.
GET upbutler.com/status/scaleway/status.agent.json
MCP: upstream_status {"service":"scaleway"}
European cloud: instances, serverless, object storage and generative APIs.
What Scaleway says
Degraded· 3 open incidents
Taken as is from Scaleway's own status page API. Incident titles and component names below are theirs.
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
- [Support] Delays in ticket processingidentified · impact minor
Since · Excellence
En raison d’un volume exceptionnellement élevé de demandes, le traitement des tickets en cours peut prendre plus de temps que d’habitude. Nos équipes sont pleinement mobilisées afin de rétablir la situation et de traiter les demandes dans les meilleurs délais. Nous vous remercions pour votre patience et votre compréhension. Due to a high volume of requests, the processing of ongoing tickets may take longer than usual. Our teams are fully mobilized to restore normal service and handle requests a…
- [Support] Call Handling Delaysidentified · impact minor
Since · Excellence
Due to a high volume of requests, it may be difficult to reach our teams by phone. If needed, we invite you to contact us directly by submitting a ticket so that your request can be processed as quickly as possible. Thank you for your understanding. En raison d’un nombre élevé de demandes, il peut être difficile de joindre nos équipes par téléphone. Au besoin, nous vous invitons à nous contacter directement par ticket afin que votre demande soit prise en charge dans les meilleurs délais. Merci…
- [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.
- [DEDIRACK][DC1] Changes to access control during building worksmaintenance in progress
Since · DC1, Dedirack
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Text written by Scaleway, shown unchanged.
Which part of Scaleway?
Scaleway components
9 of 72 not operational
Dedibox - Products
- DediboxOperational
- HostingOperational
- SANOperational
- DedirackMaintenance
- DedibackupOperational
- DomainsOperational
- RPNOperational
- Dedibox ConsoleOperational
- Dedibox VPSOperational
Elements - Products
- AccountOperational
- APIsOperational
- Apple SiliconOperational
- Audit TrailOperational
- BillingOperational
- Block StorageOperational
- CockpitOperational
- Container RegistryDegraded
- Data WarehouseOperational
- DatabasesOperational
- Developer ToolsOperational
- DomainsOperational
- Edge serviceOperational
- Elastic MetalDegraded
- Elements ConsoleOperational
- Environmental FootprintOperational
- File StorageOperational
- Generative APIOperational
- IAMOperational
- InstancesOperational
- IoT HubOperational
- JobsOperational
- KafkaDegraded
- Kubernetes KapsuleOperational
- Load BalancerOperational
- Managed InferenceOperational
- Messaging and QueuingOperational
- NetworkOperational
- Object StorageOperational
- ObservabilityOperational
- Public GatewayOperational
- Secret ManagerOperational
- Serverless ContainerDegraded
- Serverless FunctionsDegraded
- Serverless-DatabaseOperational
- Transactional EmailOperational
- VPCOperational
- Web HostingOperational
- WebsiteOperational
- Clusters for Apache Spark™Degraded
Elements - AZ
- fr-par-1Operational
- fr-par-2Operational
- fr-par-3Operational
- nl-ams-1Operational
- nl-ams-2Operational
- nl-ams-3Operational
- pl-waw-1Operational
- pl-waw-2Operational
- pl-waw-3Operational
- it-mil-1Operational
Saagie - Products
- Product-1-ACOOperational
- Product-2-BOUOperational
- Product-3-BVOperational
- Product-6-SIPDEVOperational
- Product-7-SIPINTOperational
Dedibox - Datacenters
- DC1Maintenance
- DC2Operational
- DC3Operational
- DC4Operational
- DC5Operational
- AMSOperational
Miscellaneous
- ExcellenceDegraded
- BookMyNameOperational
Scaleway 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: maintenance
- 2026-09-16: maintenance
- 2026-09-17: maintenance
- 2026-09-18: maintenance
- 2026-09-19: maintenance
- 2026-09-20: maintenance
- 2026-09-21: maintenance
- 2026-09-22: maintenance
- 2026-09-23: maintenance
- 2026-09-24: maintenance
- 2026-09-25: maintenance
- 2026-09-26: minor incident
- 2026-09-27: minor incident
- 2026-09-28: minor incident
- 2026-09-29: minor incident
- 2026-09-30: major incident
- 2026-10-01: minor incident
- 2026-10-02: minor incident
- 2026-10-03: minor incident
- 2026-10-04: minor incident
- 2026-10-05: minor incident
- 2026-10-06: major incident
- 2026-10-07: minor incident
- 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. It is their incident record, not a measurement of uptime.
- Incidents
- 21
- 2 major or critical
- Typical time to resolve
- 5 h 13 min
- median
- Nine in ten within
- 6 days
- 90th percentile
- Longest
- 9 days
- record since 2026-09-15
Get alerted when Scaleway goes down
No account. One email when Scaleway reports an incident, 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 Scaleway's current status in a README or an internal wiki. It updates by itself.
[](https://upbutler.com/status/scaleway)Tell your outage from Scaleway's
Declare that your project depends on Scaleway. 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:
- scalewaycurl -s https://upbutler.com/status/scaleway/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "scaleway",
"verdict": "proceed",
"status": "degraded",
"reason": "[Support] Delays in ticket processing",
"retryAfterSec": null,
"incident": {
"title": "[Support] Delays in ticket processing",
"url": "https://status.scaleway.com/incidents/3mdrw07fz4sk"
},
"probe": null
}Questions
- Is Scaleway down right now?
- Partly. As of 2026-10-10 07:16 UTC, Scaleway is having issues, with an open incident: "[Support] Delays in ticket processing". This page reads the status again every 3 minutes.
- How long do Scaleway outages usually last?
- Of the 21 incidents Scaleway reported in the last 90 days, half were resolved within 5 h 13 min and nine in ten within 6 days; the longest took 9 days. These are the provider's own start and end times.
- 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.
- Can I get an alert when Scaleway 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 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 Scaleway status?
- Fetch https://upbutler.com/status/scaleway/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"}, 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.