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 57 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 23Today
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.
June 2026
[PAYMENT] - [All] - issue with AMEX card payment
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The incident is now mitigated, and we are actively monitoring the situation.
Failed AMEX payments have been retried and are processing successfully.
New orders and renewals can now be processed using AMEX as normal.
identified
We have identified the issue and are currently working on a fix.
investigating
We have noticed that payments with AMEX card are not successful.
Our engineers are investigating.
[Cockpit] - [fr-par] Grafana access issues
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience slow response times or connection errors when accessing Grafana.
May 2026
[Generative APIs] - [fr-par] Performance issues on mistral-small-3.2-24b-instruct-2506
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Customers may experience performance issues and errors when using the mistral-small-3.2-24b-instruct-2506 model due to a load increase on an internal component.
[Generative APIs] - [fr-par] Stability issues on gemma-4-26b-a4b-it
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Customers may experience performance issues and errors when using the gemma-4-26b-a4b-it model due to a load increase on an internal component.
[Generative APIs] - [fr-par] Stability issues on gemma-4-26b-a4b-it
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
The situation is now stable, we remain vigilant on the matter.
investigating
Customers may experience performance issues and errors when using the gemma-4-26b-a4b-it model due to a load increase on an internal component.
[Generative APIs] - [fr-par] Performance issues on mistral-small-3.2-24b-instruct-2506
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
Customers may experience performance issues and errors when using the mistral-small-3.2-24b-instruct-2506 model due to a load increase on an internal component.
[SUPPORT] [ELEMENTS] - Error 500 when creating or viewing a ticket
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We have received reports of a 500 error occurring when creating or opening a ticket, making these actions impossible.
[BLKS] - [PAR3-DC4]-Elevated error rates for Block Storage in the fr-par-3 zone
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating performance degradation affecting Block Storage volumes in fr-par-3.
Connectivity issues may result in intermittent request failures.
[Serverless Containers] - [fr-par] Instabilities in one cluster
Source not attested
Last archived state: resolved
View archived record details
monitoring
Everything has returned to normal for the impacted services.
We'll let the status in monitoring for the night to ensure everything is fine.
investigating
We are experiencing instability again. We are investigating.
monitoring
Everything has returned to normal for the impacted containers.
We are continuing to monitor the situation to ensure everything is fine.
investigating
Customers may experience instabilities when using Serverless Containers in the fr-par region.
[Data Warehouse] - [fr-par-1] Issues creating new data warehouses
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience issues creating new data warehouses in fr-par-1 due to a partial outage on an internal component.
Our engineers are currently working on the situation.
