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
Incident History
October 2026
[Dedibox] - [DC5] - RPN Switch bay A53 and A54 planned maintenance
We have a temporary outage on a RPN Switch bay A53 an A54 which might cause traffic issue. As such, a maintenance is planned :
14/10 - 10 AM UTC/12 AM Paris time
A short interruption (approximately 5 minutes) is to be expected.
[Dedibox] - [DC5] - Rack D38 of room 1 lost connectivity
We are currently experiencing a network incident affecting a switch in DC5, which is currently unreachable.
Our technical team is investigating the situation and working on the required recovery actions.
En raison d’un volume exceptionnellement élevé de demandes, le traitement des tickets en cours peut prendre plus de temps que d’habitude.
Nos équipes sont pleinement mobilisées afin de rétablir la situation et de traiter les demandes dans les meilleurs délais.
Nous vous remercions pour votre patience et votre compréhension.
Due to a high volume of requests, the processing of ongoing tickets may take longer than usual.
Our teams are fully mobilized to restore normal service and handle requests as quickly as possible.
Thank you for your patience and understanding.
Due to a high volume of requests, it may be difficult to reach our teams by phone.
If needed, we invite you to contact us directly by submitting a ticket so that your request can be processed as quickly as possible.
Thank you for your understanding.
En raison d’un nombre élevé de demandes, il peut être difficile de joindre nos équipes par téléphone.
Au besoin, nous vous invitons à nous contacter directement par ticket afin que votre demande soit prise en charge dans les meilleurs délais.
Merci de votre compréhension.
[Jobs] - [fr-par] - Jobs are stuck in a transient state
[Started Around 14h00 CET]
Jobs cannot be executed. Clients will see job runs stuck in transient states like validated, queued, or running.
Issue is under investigation
[Dedibox VPS] [fr-par] - servers locked in Paris location
fr-par-1fr-par-2fr-par-3Container RegistryJobsKafkaServerless ContainerServerless FunctionsClusters for Apache Spark™
investigating
We added other impacted products and we are still investigating.
investigating
We are continuing to investigate this issue.
investigating
We are currently observing an increased rate of 5xx errors on the container registry in the fr-par region. Some image push and pull operations may fail or experience delays. Our teams are actively investigating, and we will provide an update as soon as more information is available.
[15h00 utc+2]
We are experiencing instabilities with a critical part of the glm-5.2 model infrastructure, working actively on the mitigation
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.