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

October 2026
[Generative API] - [global] - GLM-5.3 timeouts
minor

View incident details and source

Started:

fr-par-1 fr-par-2 fr-par-3 nl-ams-1 nl-ams-2 nl-ams-3 pl-waw-1 pl-waw-2 pl-waw-3 it-mil-1 it-mil-2 it-mil-3 Generative API
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Started Tuesday 20th October @ 5:04pm The glm-5.3 model is consistently returning timeout errors on all requests. We are working at fixing the issue.
[fr-par] Partial unavailability affecting an Object Storage cluster
minor

View incident details and source

Started:

Object Storage
monitoring
Object Storage services in the fr-par region have returned to normal operating conditions following the deployment of the fix. Our teams continue to closely monitor the infrastructure to ensure service stability before marking the incident as resolved.
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
Following an infrastructure deployment, connectivity was disrupted across several racks, potentially impacting Object Storage customers in the fr-par region through increased latency and request errors. The issue has been identified, and our engineering teams are currently deploying a fix to restore normal service operations.
[Generative API] - [global] - Bge-multilingual-gemma-2 became unavailable
minor Observed active window 25m

View incident details and source

Started:

Generative API
investigating
Started Tuesday 20th October 2:50pm The model is not available. We're working to fix it asap.
[Cockpit] Listing data exporters results in an error
minor

View incident details and source

Started:

fr-par-1 fr-par-2 fr-par-3 nl-ams-1 nl-ams-2 nl-ams-3 pl-waw-1 Cockpit pl-waw-2 pl-waw-3 it-mil-1 it-mil-2 it-mil-3
investigating
After a faulty deployment, listing data exporters in the Cockpit Console results in error.
Degraded Performances on it-mil APIs
minor

View incident details and source

Started:

APIs it-mil-1 it-mil-2 it-mil-3
monitoring
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.
[Generative API] - [global] - Deepseek v4.1 flash timeouts
minor Observed active window 20h 2m

View incident details and source

Started:

Generative API
monitoring
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
minor Observed active window 2h 9m

View incident details and source

Started:

Serverless-Database
investigating
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.
[Dedibox] - PARDC3 / Room 4-4 / Rack C18 - PUB switch unreachable
minor Observed active window 22h 59m

View incident details and source

Started:

Dedibox
monitoring
A faulty device has been replaced.
investigating
PUB service down on devices located in PARDC3 / Room 4-4 / Rack C18  since 2026/10/18 12:30 UTC, Checks in progress
[FR-PAR-1] - Failure in cooling system
minor Observed active window 1h 2m

View incident details and source

Started:

fr-par-1 Instances
monitoring
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.
[GAPI] - [Global] - Qwen3 Embeddings produces timeouts
minor Observed active window 32m

View incident details and source

Started:

Generative API
investigating
Timeouts are observed on qwen3-embedding-8b model through the Generative API.

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.

May 2026
[Billing] - [fr-par/global] April to May cutoff delay
minor Source not attested
Last archived state: resolved
View archived record details
identified
Customers may experience missing or incorrect billing data for May due to a delay in the monthly cutoff process. Expect May consumptions and draft bill amounts to be up-to-date and reliable before 12:00 Paris time
investigating
We are currently investigating this issue.
identified
Customers may experience missing or incorrect billing data for May due to a delay in the monthly cutoff process. Expect May consumptions and draft bill amounts to be up-to-date and reliable before 12:00 Paris time
identified
Customers may experience missing or incorrect billing data for May due to a delay in the monthly cutoff process.
[Billing] - [fr-par/global] April to May cutoff delay
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience missing or incorrect billing data for May due to a delay in the monthly cutoff process.
[EDGE SERVICES] - Edge Services is currently unavailable from the outside
critical Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
The engineers on our Edge Services team are still investigating the situation.
investigating
Our Edge Services are currently unavailable; our engineers are already investigating the issue. We will update this status as soon as we have more information.
[INSTANCE] - [ALL REGION] Instance creation failure from console
major Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
A fix has been implemented and we are monitoring the results
investigating
Due to an internal issue, it is currently not possible to create new instances across all regions from the console. However, you can create them using the Scaleway CLI available here: https://cli.scaleway.com/instance/
April 2026
[Block Storage] - [fr-par-1] Snapshot API call timeouts
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
Customers may experience issues with Block Storage snapshot operations in the FR-PAR-1 region. Our engineering team has identified the root cause and is working on a solution to restore normal operations. We will provide further updates as soon as the issue is resolved. Thank you for your patience.
investigating
Some RDB instances in the FR‑PAR‑1 region are currently stuck in the "snapshotting" state. Our engineering team is actively working to release the affected instances and restore normal snapshot operations. We will provide further updates as soon as the issue is resolved. Thank you for your patience
[Object Storage] - [it-mil] S3 frontal requests failures
major Source 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 failures when accessing Object Storage in the Milan region due to an issue during an upgrade. The team is rolbacking this change. The issue started at 09:05 UTC and ended at 09:41 UTC
identified
Customers may experience failures when accessing Object Storage in the Milan region due to an issue during an upgrade. The team is rollbacking this change.
[E-mail Gateway] - [World] - Delays sending emails to ProtonMail
Source not attested
Last archived state: resolved
View archived record details
investigating
The emails that are sent to ProtonMail (including the emails sent to a custom domain associated to ProtonMail) are processed very slowly.
[Network infrastructure] - DC5 - RPN Switch reboot in rack DC5/S1/C57
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
Dedibox customers in rack DC5/S1/C57 may experienced network connectivity issues on the rpn network due to a switch reboot.
[Serverless Functions] - [fr-par/nl-ams/pl-waw] DNS resolution failures for all functions
minor Source not attested
Last archived state: resolved
View archived record details
investigating
After investigation, this also affects functions created on new namespaces on fr-par.
investigating
We are continuing to investigate this issue.
investigating
Customers may experience DNS resolution failures for their Serverless Functions in the nl-ams and pl-waw regions, due to an error that happened during the scheduled maintenance: https://status.scaleway.com/incidents/qhh06fhhn47r. Errors for clients might look like: "lookup [...] on 10.32.15.25:53: read udp 100.96.xx.xx:xx->10.32.15.25:53: i/o timeout". We have identified the root cause. Sorry about any inconvenience.
[BareMetal API] IPMI calls timeout issue
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience timeouts when performing IPMI calls, including stop, start, and reboot actions, on BareMetal servers.