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.
May 2026
[Apple Silicon] - [fr-par-1] Increased delivery & installation time for Apple Silicon machines
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience issues caused by a PostgreSQL LISTEN/NOTIFY bug in fr-par-1.
Asahi and DevOS configuration/installation workflows on Mac-Mini servers are currently unable to complete & will result in retry. This may cause machine to temporarily end up in error state or installation to take longer than usual. We are working to restablish the service as fast as possible.
[Identity and Access Management] - [world] API unavailable
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
From 10:55AM CET to 11:01AM CET, an incident occured on the IAM service. Impacts include:
-All management actions on Groups, Policies, Applications, API keys ans Users were impossible
-Some console users may have been automatically logged out
-Login on console was unavailable
-Some products with direct dependencies on IAM were partly unavailable on some limited control plane endpoints, mostly on Create endpoints: SSH keys, Kubernetes, MongoDB, Serverless products, Block Storage, Edge Service...
investigating
Customers may experience API errors when interacting with Identity and Access Management due to an internal dependency issue.
Impact from 10.55 am to 11.01 am
Generative API instabilities
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may encounter 403 or 500 errors when querying the service. The root cause has been identified, and we're working on a fix.
Due to an internal dependency, all upgrades and new cluster creations on IT-Mil are currently blocked. Our team is actively working on a solution.
[Instance Orchestration] - [fr-par-2] No public IPv4 available
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently unable to assigne IPv4 adresses in the Paris (fr-par-2) region. This may affect the creation of new instances requiring a public IPv4 address
Customers may experience connectivity issues on the WebHosting platform pf-1005.
Our teams are working to resolve the issue.
[OBJS] - [nl-AMS] Object Storage availability issues on AMS
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue on the second server have been fixed.
The major impact started from 10h37 UTC to 11h53 UTC with roughly 1% of AMS requests resulting in errors.
The team is now monitoring the situation.
investigating
Due to 2 servers of the same Object Storage cluster being down in 2 different AZ, access to data stored on that cluster can return 500 errors.
Our team is on it.
[Cockpit] - [nl-ams/pl-waw] Elevated error rates on metrics and logs
majorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience elevated error rates on metrics and logs in Cockpit on the nl-ams and pl-waw regions.
[DRPN] - [DC5 room 1 rack D13 blocks K and L] - RPN switch down
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience RPN connectivity issues with Dedibox servers in DC5 room 1 rack D13 block K and L due to an unreachable RPN switch.
Public connectivity is not affected.
Customers may experience RPN connectivity issues with Dedibox servers in DC5 room 1 rack D13 block K and L due to an unreachable RPN switch.
Public connectivity is not affected.
