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
[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.
[fr-par] Site-to-site VPN configuration issue
minor Observed active window 933h 43m

View incident details and source

Started:

fr-par-1 fr-par-2 fr-par-3 VPC
monitoring
Following a configuration issue during a deployment, numerous routes stopped being advertised, which may have impacted routing to the PAR VPN gateways.
[CKPT] - [Global] - On new projects, first attempts to connect to Grafana may result in internal error (the following ones end up working)
minor Observed active window 654h 2m

View incident details and source

Started:

Cockpit
investigating
We are currently investigating this issue.

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.

July 2026
[BRMI] - nl-ams-2 - no ssh access to server
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Installations may result in errors, and changing to rescue mode may fail in the NL-AMS-2 region specifically. We are currently investigating the issue.
[it-mil-1] - Multiple products not available
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are currently investigating this issue.
identified
Multiple products unavailable between 11:45 UTC and 12:00 UTC annotation audit trail cockpit containers datalab datawarehouse instance v1 k8s kafka kms mongo registry secrets
[GAPI] - Gemma-4 infinite loops in response instabilities
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Users might experiment infinite loops in responses in case of multi turn tool_call requests using model gemma-4-26b-a4b-it
[EM] [DDX] (PAR-1 DC2) Some servers are down on rack E6 room 103
Source not attested
Last archived state: resolved
View archived record details
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
For an unknown reason, half of rack E6 room 103 is down (PAR1- DC2)
[DEDIBOX] [DC2]- 1 rack lost public connectivity
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Due to a network equipment failure, Dedibox servers in the following racks at the OPCORE datacenter are affected: - s202A-B7
investigating
Due to a network equipment failure, Dedibox servers in the following racks at the OPCORE datacenter are affected: - s202A-B7
[BMNA] - Certificate imap.bookmyname.com seems to be incorrect
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating an issue with the SSL certificates on imap.bookmyname.com and smtp.bookmyname.com. This issue may prevent some users from sending or receiving emails through these endpoints.
[API Gateway] - [it-mil] - connection failures
minor Source not attested
Last archived state: resolved
View archived record details
identified
Since around 1 PM UTC, some internal connections to Scaleway API on it-mil region started to fail. As a result: -Pushes to rg.it-mil.scw.eu are failing with HTTP 500 -Serverless Containers deployments are failing (resources stuck in creating) -etc. (list is not exhaustive)
[CAAS] - [fr-par] - namespaces and containers stuck in transient statuses
minor Source not attested
Last archived state: resolved
View archived record details
identified
Following incident on Compute instances (https://status.scaleway.com/incidents/bsp2y5fysy9w), a few Serverless Containers and namespaces on fr-par region have been stuck in transient statuses (updating/deleting) during the night. Not all resources were impacted, only a fraction on one part of our infrastructure (~1/10). On this part, impacted resources were either: - updated between 2026-07-21 21:07 UTC and 2026-07-21 22:05 UTC - or deleted between 2026-07-21 21:33 UTC and 2026-07-22 03:18 ...
[KUBERNETES] - [fr-par] - Product API down
major Source not attested
Last archived state: resolved
View archived record details
monitoring
The situation has returned to normal
investigating
We are currently investigating this issue.
monitoring
The Kapsule public API is available again.
investigating
Product API is down for Kubernetes clusters
[fr-par-1] - Issue with Compute Instances
major Source not attested
Last archived state: resolved
View archived record details
monitoring
The situation has returned to normal
investigating
We are currently investigating this issue.
monitoring
The Kapsule public API is available again.
investigating
The situation is stable. All products are now operational except for the Kapsule public API, which is still unavailable.
investigating
Disk I/O operations are starting to recover, which should begin resolving the issue for the instances.
investigating
Our team is currently working on solving the issue.
investigating
We are still investigating this critical issue with the utmost priority.
investigating
We are continuing to investigate this issue.
investigating
Following a crash of one node on the block storage cluster at 20h15 UTC, some VMs are stuck. The oncall team is investigating it.