Skip to main content
Scaleway logo

Is Scaleway Down?

No — Scaleway is up

Reachable from all 8 checked regions

Average response time: 566ms

Last checked · checks run every 6 hours

Official status page: https://status.scaleway.com

[Support] Delays in ticket processing

minor identified

Processing of current tickets may take longer than usual. Our teams are currently working to restore the service as soon as possible. Thank you for your understanding.

Components the vendor reports as affected: DC1 Under Maintenance Dedirack Under Maintenance Dedibackup Degraded Performance

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Scaleway fail from enough regions to rule out probe noise.

Scaleway uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
569ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 34 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

34-day clean streak
Aug 24: 100.00% uptime, 40 checks
Aug 25: 100.00% uptime, 32 checks
Aug 26: 100.00% uptime, 32 checks
Aug 27: 100.00% uptime, 32 checks
Aug 28: 100.00% uptime, 32 checks
Aug 29: 100.00% uptime, 32 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 32 checks
Sep 3: 100.00% uptime, 31 checks
Sep 4: 100.00% uptime, 28 checks
Sep 5: 100.00% uptime, 22 checks, 1 incident
Sep 6: 100.00% uptime, 32 checks
Sep 7: 100.00% uptime, 31 checks
Sep 8: 100.00% uptime, 31 checks
Sep 9: 100.00% uptime, 38 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 16 checks
Aug 24 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

jnb
767ms
DNS 0ms TCP 0ms TLS 9ms TTFB 723ms
lax
647ms
DNS 0ms TCP 1ms TLS 9ms TTFB 634ms
lhr
218ms
DNS 0ms TCP 2ms TLS 11ms TTFB 206ms
nrt
696ms
DNS 0ms TCP 1ms TLS 9ms TTFB 686ms
ord
799ms
DNS 7ms TCP 2ms TLS 12ms TTFB 781ms
sin
566ms
DNS 1ms TCP 1ms TLS 6ms TTFB 557ms
sjc
283ms
DNS 0ms TCP 2ms TLS 8ms TTFB 273ms
syd
555ms
DNS 0ms TCP 1ms TLS 13ms TTFB 546ms

What Scaleway does

Scaleway is a European cloud provider offering compute instances, bare metal, managed Kubernetes, object storage, databases and serverless products, alongside the older Dedibox dedicated server range. It runs regions in Paris, Amsterdam, Warsaw and Milan. Customers who choose it for data residency inside Europe depend on it the way others depend on the larger hyperscalers.

What an outage looks like

Instances become unreachable or fail to launch in one availability zone while others are fine. The Elements console will not load, so nothing can be provisioned even where the infrastructure is healthy. Object Storage returns errors on read or write. Kubernetes Kapsule clusters lose contact with their control plane, and Load Balancer health checks start failing across the affected zone.

What to do about it

status.scaleway.com reports per product and per availability zone, listing fr-par-1 to fr-par-3, nl-ams-1 to nl-ams-3, pl-waw-1 to pl-waw-3 and it-mil-1, with the legacy Dedibox estate tracked separately. Identify your zone before assuming a regional outage. If workloads already span zones, shifting traffic away from the affected one beats waiting, and a console outage does not stop running instances.

Is it down for everyone, or just you?

If this page says Scaleway is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Scaleway outage FAQ

Is all of Scaleway down or just my zone?
Almost always just a zone. Scaleway reports availability zones individually, including fr-par-1 to fr-par-3 in Paris, nl-ams-1 to nl-ams-3 in Amsterdam, pl-waw-1 to pl-waw-3 in Warsaw and it-mil-1 in Milan. Find the zone your resources run in and read that row, since a Paris problem tells you nothing about Amsterdam.
The console will not load. Are my servers still running?
Usually yes. Scaleway tracks the Elements Console and the APIs as components separate from Instances and the rest of the infrastructure. A console outage stops you provisioning and managing resources, not the resources themselves. Check whether your services still answer traffic directly rather than judging from an interface you cannot reach.
Does Scaleway's status page cover Dedibox?
Yes, and separately. The status page lists Dedibox with its own sub-components including Hosting, SAN, Dedirack, Dedibackup, RPN, the Dedibox Console and Dedibox VPS, and it tracks datacentres DC1 to DC5 and AMS individually. Dedibox customers should read those rows rather than the cloud product rows, which describe a different estate entirely.
Should I fail over to another zone during an incident?
If the architecture already supports it, yes, and that is exactly what zone redundancy is for. Moving traffic to a healthy zone is usually faster than an incident resolves. Building failover during the outage is not realistic, so the decision that matters was whether you set it up beforehand, not what you do now.
Does an outage affect Object Storage and compute together?
Not necessarily. Scaleway lists Object Storage, Block Storage, File Storage and Instances as separate components, and they can fail independently within the same zone. An application can keep serving from healthy instances while uploads to Object Storage fail. Read the specific component rows rather than assuming one zone incident affects everything inside it.

How we measure this

  • We request Scaleway's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Scaleway publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Scaleway goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required