Skip to content

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.com

What 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

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

  1. 2026-07-13: no record
  2. 2026-07-14: no record
  3. 2026-07-15: no record
  4. 2026-07-16: no record
  5. 2026-07-17: no record
  6. 2026-07-18: no record
  7. 2026-07-19: no record
  8. 2026-07-20: no record
  9. 2026-07-21: no record
  10. 2026-07-22: no record
  11. 2026-07-23: no record
  12. 2026-07-24: no record
  13. 2026-07-25: no record
  14. 2026-07-26: no record
  15. 2026-07-27: no record
  16. 2026-07-28: no record
  17. 2026-07-29: no record
  18. 2026-07-30: no record
  19. 2026-07-31: no record
  20. 2026-08-01: no record
  21. 2026-08-02: no record
  22. 2026-08-03: no record
  23. 2026-08-04: no record
  24. 2026-08-05: no record
  25. 2026-08-06: no record
  26. 2026-08-07: no record
  27. 2026-08-08: no record
  28. 2026-08-09: no record
  29. 2026-08-10: no record
  30. 2026-08-11: no record
  31. 2026-08-12: no record
  32. 2026-08-13: no record
  33. 2026-08-14: no record
  34. 2026-08-15: no record
  35. 2026-08-16: no record
  36. 2026-08-17: no record
  37. 2026-08-18: no record
  38. 2026-08-19: no record
  39. 2026-08-20: no record
  40. 2026-08-21: no record
  41. 2026-08-22: no record
  42. 2026-08-23: no record
  43. 2026-08-24: no record
  44. 2026-08-25: no record
  45. 2026-08-26: no record
  46. 2026-08-27: no record
  47. 2026-08-28: no record
  48. 2026-08-29: no record
  49. 2026-08-30: no record
  50. 2026-08-31: no record
  51. 2026-09-01: no record
  52. 2026-09-02: no record
  53. 2026-09-03: no record
  54. 2026-09-04: no record
  55. 2026-09-05: no record
  56. 2026-09-06: no record
  57. 2026-09-07: no record
  58. 2026-09-08: no record
  59. 2026-09-09: no record
  60. 2026-09-10: no record
  61. 2026-09-11: no record
  62. 2026-09-12: no record
  63. 2026-09-13: no record
  64. 2026-09-14: no record
  65. 2026-09-15: maintenance
  66. 2026-09-16: maintenance
  67. 2026-09-17: maintenance
  68. 2026-09-18: maintenance
  69. 2026-09-19: maintenance
  70. 2026-09-20: maintenance
  71. 2026-09-21: maintenance
  72. 2026-09-22: maintenance
  73. 2026-09-23: maintenance
  74. 2026-09-24: maintenance
  75. 2026-09-25: maintenance
  76. 2026-09-26: minor incident
  77. 2026-09-27: minor incident
  78. 2026-09-28: minor incident
  79. 2026-09-29: minor incident
  80. 2026-09-30: major incident
  81. 2026-10-01: minor incident
  82. 2026-10-02: minor incident
  83. 2026-10-03: minor incident
  84. 2026-10-04: minor incident
  85. 2026-10-05: minor incident
  86. 2026-10-06: major incident
  87. 2026-10-07: minor incident
  88. 2026-10-08: minor incident
  89. 2026-10-09: minor incident
  90. 2026-10-10: minor incident
2026-07-1315 of 26 days with an incidenttoday

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
Started (UTC)IncidentImpactLasted
[Jobs] - [fr-par] - Jobs are stuck in a transient stateminor35 min
[Dedibox VPS] [fr-par] - servers locked in Paris locationminor1 h 39 min
[Cockpit]- it-mil - api downminorunder a minute
[Key Manager] - it-mil - api unavailableminor47 h 36 min
[Generative APIs] - [fr-par] - glm-5.2 service instabilitiesminor3 days
[DOMAINS] API communication lostmajor1 min
[DC5] Public Switch in rack b11 room 1 is downminor3 h 17 min
[Support] Call Handling Delaysminor46 h
[DC5] Several Switch and server down Row B and Dminor26 h 52 min
[Web Hosting] - Intermittent access on pf-1004 platformminor50 min
[Dedibox VPS] - [fr-par] servers locked in Paris locationminor10 h 21 min
[SERVERLESS-JOBS] [FR-PAR] Jobs can't be executedminor5 h 48 min
[TEM] - TEM IP address blacklistminor12 min
[Account] - Global - Account API Downmajor5 h 13 min
[Serverless SQL DB] - [fr-par] Daily backup didn't work last nightminor3 h 15 min
[FR-PAR] Network perturbationsminor7 days
[AGWX] Stabilities issues in fr-parminor19 min
RPN - AMS1/AMS - rpn service unreachable for rack 6.12.71minor3 h 57 min
[COKPIT] [fr-par] (custom-metrics) Some unavailability errors were reportedminor9 days
[OBJS] pl-waw: Operations are slowminor46 h 33 min
[GenAPI] gpt-oss error rate increaseminor6 days

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.

Scaleway status badge

[![Scaleway status](https://upbutler.com/status/scaleway/badge.svg)](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
# upbutler.yaml
dependencies:
  - scaleway
Ask before you retry
curl -s https://upbutler.com/status/scaleway/status.agent.json
status.agent.json (live)
{
  "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.