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
[Serverless SQL DB] - [fr-par] Daily backup didn't work last night
minor Observed active window 3h 14m

View incident details and source

Started:

fr-par-1 fr-par-2 fr-par-3 Serverless-Database
identified
[03:00]: Following the temporal migration of yesterday, the daily backups of Serverless SQL DB didn't work last night. Backups are expected to become available again later today.
[FR-PAR] Network perturbations
minor Observed active window 162h 40m

View incident details and source

Started:

fr-par-1 fr-par-2 fr-par-3
monitoring
We have observed local perturbations on the backbone network of FR-PAR region, fixes have been deployed, we are monitoring the situation
[AGWX] Stabilities issues in fr-par
minor Observed active window 20m

View incident details and source

Started:

fr-par-1 fr-par-2 APIs fr-par-3
investigating
Instabilities when contacting Scaleway APIs
RPN - AMS1/AMS - rpn service unreachable for rack 6.12.71
minor Observed active window 3h 58m

View incident details and source

Started:

AMS RPN
investigating
We are continuing to investigate this issue.
investigating
The rpn device inside the rack 6.12.71 in Amsterdam is currently unreachable. At this time, the root cause has not yet been identified. Our Network team is investigating the issue and will provide further updates as soon as more information becomes available.
[COKPIT] [fr-par] (custom-metrics) Some unavailability errors were reported
minor Observed active window 218h 43m

View incident details and source

Started:

Cockpit
identified
Incident is resolved, we are still monitoring to make sure that everything runs smoothly
investigating
Some users report errors in custom metrics ingestion since 2026-09-16 We are investigating to find out the scope of the incident.
[OBJS] pl-waw: Operations are slow
minor Observed active window 46h 31m

View incident details and source

Started:

pl-waw-1 pl-waw-2 pl-waw-3 Object Storage
monitoring
The issue has been identified, fixes have been deployed, we're back to the nominal state, monitoring.
investigating
Since the 25/09 (last friday), the S3 pl-waw region is overloaded with operations. We're currently working to mitigate that.
[GenAPI] gpt-oss error rate increase
minor Observed active window 133h 30m

View incident details and source

Started:

APIs
investigating
We are observing an unexpected increase in 5xx error rate. Investigations are underway.
[EDGE] Faulty cache server
minor Observed active window 72h 4m

View incident details and source

Started:

Edge service
identified
Edge Services may return truncated HTTP content due to a faulty cache server. The incident is mitigated.
[fr-par] Qwen 3 235B saturated
minor Observed active window 204h 8m

View incident details and source

Started:

Generative API
investigating
[18:30] Qwen3 235b model performance is degraded, a few timeouts have been observed [21:30] Performance is still sub-optimal but timeouts are mostly gone
[WebHosting] Intermittent access to Rouncudbe Webmail on Dedibox infra
minor Observed active window 30m

View incident details and source

Started:

Hosting
investigating
We are currently investigating on an issue on the webmail interface.

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.

June 2026
[WebHosting Elements] - [fr-par] High load on pf-012 platform
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience degraded performance on their websites and email services hosted on the pf-012 platform due to high load on an internal component.
[GAPI] - [fr-par2] - mistral-small-3.2 errors rate increasing
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
The situation is back to nominal state, the root cause has been identified and incident responses are back to normal.
identified
Part of our Mistral Small 3.2 infrastructure start becoming un stable with un usual error rates.
[Object Storage] - [fr-par-2] - Thermal shutdown for several storage pods
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Due to abnormal temperature, some storage nodes are being shutdown to prevent data loss. This will impact acces to some objects with one-zone storage class
[RDB] - [fr-par] Managed Database provisioning delays
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience delays when provisioning new Managed Database instances or performing operations that require infrastructure changes in the fr-par region due to an issue with an internal dependency.
[Cockpit]-[fr-par] - memory pressure on product-frontend
minor Source not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
monitoring
We are continuing to monitor for any further issues.
monitoring
Between 11:50 a.m. and 1:30 p.m., metrics ingestion on FR-PAR was affected due to an operation performed on one of the components to improve its resilience. Metrics and log data are also affected.
[NATS, Queues, Topics & Events] - [fr-par] Monitoring data missing
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
Customers may experience missing monitoring data for NATS, Queues, Topics & Events in the fr-par region.
[Dedibox RPN-SAN] - [DC2/DC3] Storage failures on SAN HA pair HDD-18
major Source not attested
Last archived state: resolved
View archived record details
monitoring
Situation is now stable, we are closely monitoring situation on both members of HA pair.
monitoring
Customers may experience iSCSI connection failures on Dedibox RPN-SAN HA HDD-18 in DC2/DC3. The issue has been identified and is currently being monitored. We apologize for any inconvenience caused and will provide further updates as soon as possible.
investigating
Customers may iSCSI connections failures on Dedibox RPN-SAN HA HDD-18.
[Kafka] - [fr-par] Control plane partial outage
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience partial outages when managing Kafka resources due to an issue on the control plane.
[Network infrastructure] - [DC5][PAR-2] Public network issue
critical Source not attested
Last archived state: resolved
View archived record details
monitoring
During routine maintenance, a new configuration was deployed to our backbone routers managing traffic for fr-par-2. An unforeseen configuration conflict resulted in a total loss of public connectivity (blackholing) for all Elastic Metal servers. The configuration was pushed at 08:42 UTC for both IPv4 and IPv6. IPv4 was rollback at 09:20 and IPv6 was rollback at 09:45, restoring all connectivity.
monitoring
The fix has been deployed. Services are up and running. We are monitoring the situation and we will provide more information.
identified
The root cause has been found. A fix is being deployed.
investigating
Customers may experience a partial outage of public network connectivity on Elastic Metal servers in PAR2 (DC5).
[DC5] - Switch unreachable in rack B61
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Customers may experience connectivity issues with servers in rack B61 due to an unreachable switch in the network infrastructure.