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
[Cockpit] Listing data exporters results in an error
A fix has been implemented and we are monitoring the results.
investigating
We are currently experiencing degraded performance with it-mil APIs. Some requests may see elevated latency, intermittent errors, or timeouts. Our engineering team is actively investigating the issue and working to restore normal service as quickly as possible.
A fix has been implemented and we are monitoring the results.
identified
19th October from 2:30pm to 7pm
Some requests to the deepseek-v4.1-flash model have experienced elevated timeouts.
We have implemented a mitigation, and error rates are improving. We're monitoring the situation.
[Serverless-Database]- [fr-par] - slow cold start for the DB and DB in status error
Since Saturday October 18, 2026 at 07:55 UTC (09:55 Paris time), Serverless SQL Databases as occured slow cold start for the DB and DB in status error.
Temperatures are decreasing following an intervention by our service provider.
investigating
Servers in room 108 experience temperature increase.
This lead to CPU throttling and may result into unreachable instance.
We are working with our datacenter provider to fix the situation.
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.
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.
August 2026
Scheduled Maintenance of one of the core routers in the AMS region.
minorSource not attested
Last archived state: resolved
View archived record details
investigating
One of the two main routers will be taken out of service.
During this period, the network connection will not be redundant in all availability zones of the region "The Netherlands - Amsterdam".
No packet loss or latency changes are expected.
Date: 19.08.2026
Time: 09:00
Duration: 3 hours
[EDGE] - 503 error
minorSource not attested
Last archived state: resolved
View archived record details
Edge service
identified
The issue has been identified and a fix is being implemented.
investigating
Customer may experience 503 errors on edge service.
[FR-PAR] Serverless Databases issue
Source not attested
Last archived state: resolved
View archived record details
Serverless-Database
monitoring
Customer databases were unavailable between 8.54 am and 9.26 am. Our team had already fix but still monitoring this issue.
[CKPT] - [global] - Grafana is partially unavailable
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Some customers cannot access Grafana. We are investigating.
[PGW] - [fr-par-1] - Public Gateway stuck in transient state
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have identified that the product Public Gateway creation/update in fr-par-1 were stuck in a transient state.
The incident has been mitigated.
[NETI] - [DC3] - Dedibox RPN switch in DC3 (room 4-3, rack C9) is down
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Switch s43-c9.rpn.dc3 is down.
There is no RPN connection for the servers in DC3, room 4-3, rack C9
We are continuing to monitor for any further issues.
monitoring
The incident has now been mitigated.
investigating
We are continuing to investigate this issue.
investigating
We are investigating performance degradation affecting Block Storage in the fr-par region. Our engineering teams are actively working to identify the root cause. We will provide further updates as more information becomes available.
[DC2] Public switch issue in DC2 room 205 rack E1
minorSource not attested
Last archived state: resolved
View archived record details
identified
We have detected a switch down in DC2 room 205 rack E1
Servers in that rack currently have no public network access and are unreachable.
[fr-par-1] - Unable to execute actions on Instances
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Some actions cannot be applied on Instances on fr-par-1, resulting in resources stucks in a transient state.
July 2026
[TREM] - Service down
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Service up again, but could suffer from latency, we are monitoring the situation.
Unfortunately, the webhook event data history are currently lost.
investigating
Some instability and a down of the service, our team is in investigation to resolve the issue
