New Multi-region uptime checks and custom-domain status pages

Scaleway Outage History

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

Jul 23Oct 20

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 22 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

September 2026
san-dc2-7 unreachable
minor Observed active window 89h 39m

View incident details and source

Started:

SAN
monitoring
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.
[INSTANCE][FR-PAR-2] Outbound connectivity issues
minor Observed active window 1h 37m

View incident details and source

Started:

fr-par-2 Instances
monitoring
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
[GAPI] - Dedicated deployment cannot start properly
minor Observed active window 14h 6m

View incident details and source

Started:

Generative API
investigating
[17:20] A network issue causes an internal component to be unreachable, preventing the dedicated deployment to start properly.
[Dedibox] DC5 - room 9 - rack D31 - RPN switch down
minor Observed active window 1h 2m

View incident details and source

Started:

Dedibox DC5
identified
The RPN switch is unreachable, servers in this rack lost their RPN connectivity: sd-186972 to sd-186925
[Serverless Containers] - [mil] - API instabilities
minor Observed active window 3h 14m

View incident details and source

Started:

it-mil-1 Serverless Container
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
identified
All operations on Serverless Containers resources are impacted. Serverless Containers already deployed are reachable.
[WBHE] - [fr-par] - Customer websites are slow on pf-014.whm.fr-par.scw.cloud
minor Observed active window 55m

View incident details and source

Started:

Web Hosting
investigating
Customer websites are slow on pf-014.whm.fr-par.scw.cloud due to an overload of the server.
[Support] Delays in ticket processing
minor Observed active window 548h 53m

View incident details and source

Started:

Excellence
identified
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.
[Support] Phone assistance is unavailable
minor Observed active window 166h 40m

View incident details and source

Started:

Excellence
investigating
We are continuing to investigate this issue.
investigating
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.
[NETI] - DC2/S103/A7 - Public switch reboot
minor Observed active window 1h 16m

View incident details and source

Started:

Dedibox DC2
investigating
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.
[generative-apis] - [fr-par ] - gemma4 unhealthy
minor Observed active window 435h 3m

View incident details and source

Started:

Generative API
investigating
[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.

July 2026
[Cockpit] - [nl-ams] Ingestion errors on custom metrics
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are continuing to investigate this issue.
investigating
Customers may experience gaps in logs from Scaleway products for the time range 10:30-12:00 CEST
[Container Registry] - [world] - Missing tags on regional endpoints
minor Source not attested
Last archived state: resolved
View archived record details
identified
The issue has been found, fixed, tested and is being rolled out.
[Container Registry] - [world] - Missing tags on regional endpoints
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been found, fixed, tested and is being rolled out.
investigating
Customers may experience missing tags when listing tags on Container Registry regional endpoints. Pulling images by tag or digest is not impacted. The Container Registry API is not impacted and returns the correct list of tags.
[Network infrastructure] - [DC3] Room 4 4-6 rack 1 - Public switch is unreachable
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience a partial outage of public connectivity on servers attached to the public switch Room 4 4-6 rack 1 in DC3.
[Cockpit] - [fr-par] Traces ingestion and query degraded
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience degraded performance when ingesting or querying traces in Cockpit in the fr-par region
[Managed Inference] - [fr-par] Increase duration of deployment creation time
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience longer deployment creation times on Managed Inference in fr-par
[Serverless Containers] - [nl-ams] Connectivity issues
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
Update: Connectivity has been partially restored at around 9:30 AM. We are monitoring the situation.
investigating
Starting from 07:30 CET, users may experience connectivity issues or failed requests when accessing their Serverless Containers in the nl-ams region. This issue is under investigation by our team.
[Generative APIs] - mistral-medium-3.5-128b might be unresponsive
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience unresponsiveness when using the mistral-medium-3.5-128b model due to an instability on an internal component.
WebHosting Elements and WebHosting Dedibox
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Maintenance for security system update. A downtime of 10 min can be expected during the maintenance Date/time: July 9th from 16h to 17h
[Managed Datalab] - [fr-par] Spark cluster creation failures
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience failures when creating Spark clusters in the fr-par region due to an issue with an internal dependency.