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
[DC3] - Public Switch Unreachable at DC3, Rack S46-E16
We found the root cause and applied a patch in order to recover the service.
However, while further incidents cannot be entirely ruled out, our technical teams are actively working to identify and implement the necessary measures to prevent recurrence.
investigating
We are currently experiencing an issue with the public switch located in Rack S46-E16 at Opcore-DC3.
The switch is currently unreachable, and the root cause of the issue is still under investigation.
As a result, all customer servers connected to this switch are currently unreachable.
Our team is investigating the situation and will provide further updates as soon as more information becomes available.
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.
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.
April 2026
[Instances] - it-mil-1 - api-metadata in unreachable
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Due to an ongoing issue with an internal API service, Cloud-init may fail to load the Scaleway datasource, which means Instances may end up in an unconfigured state. We have identified the culprit and are actively working on a resolution.
Customers may experience network connectivity issues on Room 108 Rack A7 in DC2 due to a configuration error on an internal component.
[BLOCK STORAGE] - [fr-par] - High latencies on part of infrastructure
Source not attested
Last archived state: resolved
View archived record details
monitoring
All side effects have been managed. We continue to monitor the situation.
investigating
Block Storage issue is now corrected.
We are still working on managing possible impacts on other products.
investigating
We are currently experiencing increased latencies on one of our clusters in the PAR-1 region, since 13:20 UTC.
This situation may also impact other services relying on this infrastructure: Mongo DB, Postgresql DB, MySQL DB, Serverless, Data Warehouse, Cockpit, ServerlessDB.
Our teams are actively working on.
The situation has slightly improved since the beginning of the mitigation actions, and additional measures will be implemented shortly to further reduce the impact.
[Data Warehouse] - fr-par - New S3 API keys not working
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience access issues with newly generated S3 API keys due to insufficient bucket permissions. We are currently investigating the root cause.
[Instance Orchestration] - [pl-waw] Instance orchestrations APIs may encounter failures
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue has been identified and resolved, and we are monitoring the situation to ensure stability.
identified
Customers may experience issues with Instance Orchestration APIs due to an internal component failure during routine deployments.
We are working on restoring the APIs as soon as possible.
[Dedibackup] - DC3 - 500 errors on Dedibackup
minorSource not attested
Last archived state: resolved
View archived record details
identified
Some customers may experience 500 errors when trying to connect to Dedibackup in fr-par-1.
investigating
Some customers may experience 500 errors when trying to connect to Dedibackup in DC3.
[Container Registry] - [nl-ams]- High error rate on registry API
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Customers may experience a high error rate on the Container Registry API.
[DC5] Public switch issue in DC5 Room 1 1 Rack D39
minorSource not attested
Last archived state: resolved
View archived record details
identified
The Switch is currently down and is being replaced.
investigating
We have detected that public switches were down in DC5 Room 1 1 Rack D39.
Servers in that rack currently have no network access and are unreachable, RPN network is still reachable.
[DDBX]-Installation broken for windows 2019/2022
minorSource not attested
Last archived state: resolved
View archived record details
investigating
An incident is currently occurring on the Windows systems :
- Windows 2019 Hyper-V
- Windows 2019 Standard
- Windows 2019 Datacenter
- Windows 2022 Standard
- Windows 2022 Datacenter
We are currently investigating this issue.
[PAYMENT] - Payment result handling issue
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Some customers paying by card may experience a display issue where the invoice shows "unpaid" even though it has been paid.
We apologize for any inconvenience this may cause.
