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
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 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
A hardware issue impacted a RPN node (dc2-7) from 17/09/26 12h11 UTC to 18/09/26 13h01.
The service is now up for the clients using this node
We are monitoring closely for any new issues on the node and may need another downtime if the hardware issue persist.
The issue should be resolved in most destinations, our team is taking the necessary steps to ensure it works everywhere.
investigating
We are currently investigating a network issue affecting instances with an IP address in the 78.232.0.0/21 range. Outbound traffic from these instances may fail to reach a significant part of the internet. Our teams are actively working on it and we will provide an update as soon as we have more information.
The incident began on September 15 at 5:00 p.m. UTC+1
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.
Due to an issue with our phone system, only ticket and live chat assistance are currently available.
We are currently investigating the situation and will update this status as soon as we have more information.
At 3:45 am. CEST on 11/09/2026, the public switch located in DC2, room S103, rack A7, has rebooted.
All servers attached to it have lost public connectivity for around 10 minutes.
[09/09 - 16:50]
The Gemma 4 models started to show un usual latencies resulting in requests timeout
[10/09 - 9:00]
The incident has been mitigated and response times are back to normal
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
minorSource 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
minorSource 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
minorSource 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
minorSource 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
minorSource 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
minorSource 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
minorSource 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
majorSource 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
majorSource 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.
