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.
April 2026
[DC5] Private switch issue in room 1 rack c57 unreachable
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We have detected a switch down in room 1 rack c57 in DC5
Servers in that rack currently have no private network access and are unreachable.
27.04.2026 10h00 UTC
The issue has been forwarded to our team for resolution.
[Network infrastructure] - DC2 - Public switch in S301/D19 is unreachable
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience a partial outage on public connectivity for servers located in this rack.
We are currently investigating this issue.
[Network infrastructure] - DC5 - rpn switch s1-c57-3.rpn.dc5 is unreachable
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Since 8:50am CET, customers may experience network connectivity issues on servers attached to the rpn switch s1-c57-3.rpn.dc5 in DC5.
We are currently investigating this issue.
[REGX] - [fr-par] - timeout for some requests
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
Due to a database issue, some requests to the registry API did timeout
[Object Storage] - [fr-par] Timeouts on object uploads
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have implemented corrective measures. Performance should return to normal. We have planned further actions to resolve the issue long-term.
investigating
We are continuing to investigate this issue.
investigating
Customers may experience timeouts when uploading objects to Object Storage in the fr-par region due to an issue with an internal component.
[DC2] Public switch issue in DC2; room 205; H8
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We have detected a switch down in DC2; room 205; H8
Servers in that rack currently have no public network access and are unreachable.
21.04.y2026 21.30 UTC
The issue has been forwarded to our team for resolution.
[KUBE] - [fr-par/nl-ams/pl-waw] - unable to provision new nodes
minorSource not attested
Last archived state: resolved
View archived record details
identified
Due to an internal error, we're unable to provision new nodes.
[SUPPORT] - We are currently experiencing some issues with our phone system
Source not attested
Last archived state: resolved
View archived record details
identified
We are currently experiencing some issues with our phone system.
We will post an update here as soon as we have additional information.
[PAYM] - [all] - Issues adding cards via Stripe
minorSource not attested
Last archived state: resolved
View archived record details
investigating
The issue has been fixed.
If you are still encountering an issue with Stripe payment, it is related to your bank. Please contact them to unlock the situation and allow the payment to go through Stripe. Or add another payment method.
investigating
We are currently investigating an issue affecting some card operations processed through Stripe. This may impact both the addition of new cards and, potentially, some payments requiring Stripe authentication.
[Cockpit] - [fr-par] Elevated 5xx errors on logs ingestion
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience elevated 5xx errors on logs ingestion in fr-par.
