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
[Serverless SQL DB] - [fr-par] Daily backup didn't work last night
minor Observed active window 3h 14m

View incident details and source

Started:

fr-par-1 fr-par-2 fr-par-3 Serverless-Database
identified
[03:00]: Following the temporal migration of yesterday, the daily backups of Serverless SQL DB didn't work last night. Backups are expected to become available again later today.
[FR-PAR] Network perturbations
minor Observed active window 162h 40m

View incident details and source

Started:

fr-par-1 fr-par-2 fr-par-3
monitoring
We have observed local perturbations on the backbone network of FR-PAR region, fixes have been deployed, we are monitoring the situation
[AGWX] Stabilities issues in fr-par
minor Observed active window 20m

View incident details and source

Started:

fr-par-1 fr-par-2 APIs fr-par-3
investigating
Instabilities when contacting Scaleway APIs
RPN - AMS1/AMS - rpn service unreachable for rack 6.12.71
minor Observed active window 3h 58m

View incident details and source

Started:

AMS RPN
investigating
We are continuing to investigate this issue.
investigating
The rpn device inside the rack 6.12.71 in Amsterdam is currently unreachable. At this time, the root cause has not yet been identified. Our Network team is investigating the issue and will provide further updates as soon as more information becomes available.
[COKPIT] [fr-par] (custom-metrics) Some unavailability errors were reported
minor Observed active window 218h 43m

View incident details and source

Started:

Cockpit
identified
Incident is resolved, we are still monitoring to make sure that everything runs smoothly
investigating
Some users report errors in custom metrics ingestion since 2026-09-16 We are investigating to find out the scope of the incident.
[OBJS] pl-waw: Operations are slow
minor Observed active window 46h 31m

View incident details and source

Started:

pl-waw-1 pl-waw-2 pl-waw-3 Object Storage
monitoring
The issue has been identified, fixes have been deployed, we're back to the nominal state, monitoring.
investigating
Since the 25/09 (last friday), the S3 pl-waw region is overloaded with operations. We're currently working to mitigate that.
[GenAPI] gpt-oss error rate increase
minor Observed active window 133h 30m

View incident details and source

Started:

APIs
investigating
We are observing an unexpected increase in 5xx error rate. Investigations are underway.
[EDGE] Faulty cache server
minor Observed active window 72h 4m

View incident details and source

Started:

Edge service
identified
Edge Services may return truncated HTTP content due to a faulty cache server. The incident is mitigated.
[fr-par] Qwen 3 235B saturated
minor Observed active window 204h 8m

View incident details and source

Started:

Generative API
investigating
[18:30] Qwen3 235b model performance is degraded, a few timeouts have been observed [21:30] Performance is still sub-optimal but timeouts are mostly gone
[WebHosting] Intermittent access to Rouncudbe Webmail on Dedibox infra
minor Observed active window 30m

View incident details and source

Started:

Hosting
investigating
We are currently investigating on an issue on the webmail interface.

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.