New Multi-region uptime checks and custom-domain status pages

Scaleway Outage History

Daily provider-status observations and published incident history for Scaleway.

Regional incident

Scaleway has an active regional incident; no global outage is indicated. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Scaleway for future changes.

0% of 56 verified observed days had no reported provider issue

90-Day Trend

Jul 23Oct 20

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 0% 30 30

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 22 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

September 2026
[DC5] Public switch reboot
minor Observed active window 92h 11m

View incident details and source

Started:

Dedibox DC5
investigating
Switch crashed and rebooted due to kernel panic. Public connectivity was impacted for around 5min for servers located in DC5 - Room 1 - Zone 1 - Rack D57 - Bloc D
[LBAS] - [fr-par-1] - Extra delay on Load Balancer configuration/creation
minor Observed active window 1h 20m

View incident details and source

Started:

fr-par-1 Load Balancer
investigating
Extra delay for Load Balancer configuration.
[VPC] Network Connectivity issues in pl-waw-3
minor Observed active window 624h 5m

View incident details and source

Started:

pl-waw-3 VPC
monitoring
We are continuing to monitor for any further issues.
monitoring
Between 09:00 UTC on September 1, 2026, and 13:30 UTC on September 2, 2026, some newly created infrastructure in the pl-waw-3 Availability Zone experienced temporary network connectivity issues. The issue has been fully resolved, and all services are now operating normally. No action is required on your end.
August 2026
[DDBK] - [DC3] - dedibackup unvalaible - 500 error
minor Observed active window 699h 43m

View incident details and source

Started:

Dedibackup
identified
Since August 26th, the dedibackup on DC3 has been unreachable and is returning 500 errors.
[Elastic Metal] Install issues
minor Observed active window 2h 24m

View incident details and source

Started:

Elastic Metal
investigating
During or after installation, Elastic Metal encounters an error. We are investigating.
[GAPI] - missing metrics in cockpit
minor Observed active window 25m

View incident details and source

Started:

Generative API
investigating
The Generative APIs metrics are currently missing from Cockpit. The issue is currently under investigation.
[CKPT] [FR/NL/PL] - Cockpit Logs ingestion down
minor Observed active window 47m

View incident details and source

Started:

fr-par-1 fr-par-2 fr-par-3 nl-ams-1 nl-ams-2 nl-ams-3 pl-waw-1 Cockpit pl-waw-2 pl-waw-3
investigating
On a schedule maintenance of Cockpit components, we had an issue which breaks loki ingestion on FR-PAR, NL-AMS and PL-WAW. We are actually taking a step back
[EDGE] - [GLOBAL] - latency on some nodes
minor Observed active window 4h 8m

View incident details and source

Started:

Edge service
identified
High latencies may occur on Edge Services Pipelines
[OBJS][AMS][PAR] Increased 5xx errors following the loss of a rack
minor Observed active window 24h 2m

View incident details and source

Started:

nl-ams-1 nl-ams-2 nl-ams-3 Object Storage
investigating
Due to a planned electrical maintenance, one of our rack lost its power. This has increased the 5xx error level and also increased latency on nl-ams.
[SEDB] - [fr-par] - Endpoint not displayed correctly in the console
minor Observed active window 283h 28m

View incident details and source

Started:

fr-par-1 fr-par-2 fr-par-3 Databases
identified
We quickly identified that it's about a naming change on the API side.

Legacy Incident Archive

223 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

May 2026
[Redis] - [fr-par, nl-ams, pl-war] Failing provisioning and workflows
minor Source not attested
Last archived state: resolved
View archived record details
identified
Customers may experience failing workflows on Redis such as provisioning new instances
[DDBX] - [world] - Order/renewal validation is broken
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience issues when validating VPS, webhostings and domains orders. Issue is currently being investigated. Updates will be shared as soon as we have additional details.
[Managed Inference] - [fr-par] Dedicated Deployments unavailability
major Source not attested
Last archived state: resolved
View archived record details
identified
Customers are unable to create new Dedicated Deployments in the Managed Inference service.
[Serverless SQL DB] - [fr-par] DB/API unavailable
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience unavailability on Serverless SQL DB in the fr-par region.
[LBAS] - [PAR1] - Private Networks issue on many LBs
major Source not attested
Last archived state: resolved
View archived record details
investigating
Data Warehouse experiencing issues creating new deployments
investigating
The following services are impacted by this incident : - Kapsule Control Plane API for new clusters and some existing cluster unreachable - LBs are experiencing configuration latencies, which impacts Kapsule node scaling
investigating
We are currently observing connectivity issues with Load Balancers caused by a partial outage on an internal dependency in the fr-par-1 region.
[WBHE] - Dedibox to Element migrations are failing
major Source not attested
Last archived state: resolved
View archived record details
investigating
Due to ongoing incident on BookMyName, our migration flow is failing due to nameservers unavailability. We will relaunch the migration once the BMN incident is resolved.
[API Gateway] - [pl-waw] Connectivity issues
major Source not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience connectivity issues with their APIs in the pl-waw region.
[Domain Names] All BookMyName services unavailable
critical Source not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
Nos équipes ont identifié et isolé la cause de l'incident affectant les informations de contact de vos noms de domaine. L'ensemble des clients concernés a été contacté individuellement. Le service est pleinement rétabli depuis hier à 22h00 (CET). Vous pouvez désormais administrer vos noms de domaine normalement. Veuillez noter toutefois que certaines fonctionnalités secondaires restent temporairement indisponibles ; nous prévoyons leur réactivation progressive dans les prochaine...
monitoring
Nos équipes ont identifié et isolé la cause de l'incident affectant les informations de contact de vos noms de domaine. Le service sera pleinement rétabli dans la soirée. Vous pourrez alors administrer vos noms de domaine normalement. Veuillez noter toutefois que certaines fonctionnalités secondaires resteront temporairement indisponibles. Compte tenu du rétablissement effectif du service ce jour, les renouvellements automatiques seront assurés sans interruption. Par conséquent, et...
investigating
À ce stade, nous confirmons que les noms de domaine enregistrés auprès de Bookmyname ne présentent aucun risque identifié. Les modifications intervenues sur les informations de contact associées ont été entièrement rétablies dans leur configuration initiale. À ce stade de nos investigations, nous ne sommes pas en mesure de vous informer d’une date de reprise du service. Compte tenu des délais nécessaires à l’analyse, et à titre exceptionnel et gracieux, nous procéderons...
investigating
At 08:55 CEST on May 5th, we detected an unusual activity on the BookMyName Information System. Customers may have seen a modification of their contact information related to their domain names. Due to that we have decided to shutdown all public access to BookMyname the time for us to perform the investigation. From our first round of investigation we have not seen any zone modification or domain transfer out. We will keep you updated on any progress we will make on the investigation. ...
investigating
We are continuing to investigate this issue.
investigating
All BookMyName services are unavailable, and we are currently investigating the root cause. Domain management on Scaleway and Dedibox are also impacted.
[API Gateway] - [it-mil-1] DNS resolving issues
minor Source not attested
Last archived state: resolved
View archived record details
identified
Customers may experience issues resulting using our APIs in the it-mil-1 region.
[AGWX] - [it-mil-1] - DNS resolving issues
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience DNS resolving issues resulting in service unavailability on API Gateway in the it-mil-1 region.