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.
March 2026
[Network infrastructure] - fr-par-2 - Public switch rebooted
minorSource not attested
Last archived state: resolved
View archived record details
investigating
At 21h35 UTC+1, a public switch in fr-par-2 rebooted, causing all attached servers to lose public connectivity until the switch came back online at 21h46 UTC+1.
[OBJS] - [world] - Failures on ranged request on SSE enabled objects
majorSource not attested
Last archived state: resolved
View archived record details
identified
A fix for fr-par and pl-waw region have been deployed, next regions will follow soon
identified
Ranged GetObject requests on SSE-(C/ONE) objects might fail, no impact on user data, a fix has been found and will be deployed shortly.
[MongoDB] - FR-PAR - DNS resolution failure
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently experiencing an issue with DNS resolution for entries related to the Private Network, which is affecting MongoDB SRV record lookups. This is preventing some customers from connecting to their MongoDB instances when using Private Network endpoints. Our engineering teams are actively investigating and working to resolve the issue as quickly as possible. We sincerely apologise for the inconvenience and will share updates as soon as more information becomes available.
[Serverless Containers] - [fr-par] - mandatory operation to prepare for new v1 API (2/2)
Source not attested
Last archived state: resolved
View archived record details
investigating
On April 1st (between 8 AM and 5 PM UTC), we will perform a mandatory operation in the fr-par region to prepare for the upcoming v1 API (coming soon).
This operation will be carried out in two maintenance windows:
- April 1, 2026
- April 8–9, 2026
Over the course of these three days, changes will be applied to all Serverless Containers namespaces in the fr-par region.
While this operation is seamless most of the time, users may observe the following behaviors:
- Namespaces wil...
[Serverless Containers] - [fr-par] - mandatory operation to prepare for new v1 API (1/2)
Source not attested
Last archived state: resolved
View archived record details
investigating
On April 1st (between 8 AM and 5 PM UTC), we will perform a mandatory operation in the fr-par region to prepare for the upcoming v1 API (coming soon).
This operation will be carried out in two maintenance windows:
- April 1, 2026
- April 8–9, 2026
Over the course of these three days, changes will be applied to all Serverless Containers namespaces in the fr-par region.
While this operation is seamless most of the time, users may observe the following behaviors:
- Namespaces wil...
[Cockpit] - [nl-ams] - errors on query for Scaleway Logs Datasources
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Some querier pods are not restarting after Kubernetes upgrade, causing errors when querying Scaleway Logs Datasources. This may impact the ability to view and analyze logs.
[Dedibox dedicated servers] - fr-par-1 DC3 - Room 4-6 Rack A08 PUB switch is down
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Issue is taking longer than expected.
We are still on the bridge with local technicians to bring back up the switch and it's associate services
investigating
We are currently experiencing a Public network issue in rack DC3 Room 4-6 Rack A08. This is causing a loss of internet traffic for connected dedicated servers.
Network Switch is in an incorrect state, we have asked our local technicians to replace it.
investigating
We are currently experiencing a Public network issue in rack DC3 Room 4-6 Rack A08. This is causing a loss of internet traffic for connected dedicated servers. We are investigating the root cause with our local technicians.
