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.
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.
