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
At 10:10 AM CEST the 11/9/2026, public switch located in DC3 room S45 rack C5 has rebooted.
All servers in this racks have lost public connectivity during approximately 10 minutes.
Since 08/09/26 at 4:30 AM CEST, public switch located in DC2, room 301, rack D4 is unreachable.
All dedibox servers in this rack have lost public connectivity.
APIs are on a nominal state. Situation is back to normal.
investigating
Teams are still working on the remaining problems.
investigating
Situation is stabilizing on the API side, we are still working to manage side effects.
investigating
APIs for IT-MIL are still unavailable due to remaining network issue.
investigating
The situation is returning to normal. We are currently fixing the side effects.
During the incident, management of resources on IT-MIL-1 AZ was not possible through APIs and console.
Your domain may suffer from delivery latency. Our team is working to fix this situation.
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.
March 2026
[Network infrastructure] - fr-par-2 - Public switch rebooted
minorSource not attested
Last archived state: resolved
View archived record details
investigating
At 21h35 UTC+1, a public switch in fr-par-2 rebooted, causing all attached servers to lose public connectivity until the switch came back online at 21h46 UTC+1.
[OBJS] - [world] - Failures on ranged request on SSE enabled objects
majorSource not attested
Last archived state: resolved
View archived record details
identified
A fix for fr-par and pl-waw region have been deployed, next regions will follow soon
identified
Ranged GetObject requests on SSE-(C/ONE) objects might fail, no impact on user data, a fix has been found and will be deployed shortly.
[MongoDB] - FR-PAR - DNS resolution failure
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently experiencing an issue with DNS resolution for entries related to the Private Network, which is affecting MongoDB SRV record lookups. This is preventing some customers from connecting to their MongoDB instances when using Private Network endpoints. Our engineering teams are actively investigating and working to resolve the issue as quickly as possible. We sincerely apologise for the inconvenience and will share updates as soon as more information becomes available.
[Serverless Containers] - [fr-par] - mandatory operation to prepare for new v1 API (2/2)
Source not attested
Last archived state: resolved
View archived record details
investigating
On April 1st (between 8 AM and 5 PM UTC), we will perform a mandatory operation in the fr-par region to prepare for the upcoming v1 API (coming soon).
This operation will be carried out in two maintenance windows:
- April 1, 2026
- April 8–9, 2026
Over the course of these three days, changes will be applied to all Serverless Containers namespaces in the fr-par region.
While this operation is seamless most of the time, users may observe the following behaviors:
- Namespaces wil...
[Serverless Containers] - [fr-par] - mandatory operation to prepare for new v1 API (1/2)
Source not attested
Last archived state: resolved
View archived record details
investigating
On April 1st (between 8 AM and 5 PM UTC), we will perform a mandatory operation in the fr-par region to prepare for the upcoming v1 API (coming soon).
This operation will be carried out in two maintenance windows:
- April 1, 2026
- April 8–9, 2026
Over the course of these three days, changes will be applied to all Serverless Containers namespaces in the fr-par region.
While this operation is seamless most of the time, users may observe the following behaviors:
- Namespaces wil...
[Cockpit] - [nl-ams] - errors on query for Scaleway Logs Datasources
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Some querier pods are not restarting after Kubernetes upgrade, causing errors when querying Scaleway Logs Datasources. This may impact the ability to view and analyze logs.
[Dedibox dedicated servers] - fr-par-1 DC3 - Room 4-6 Rack A08 PUB switch is down
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Issue is taking longer than expected.
We are still on the bridge with local technicians to bring back up the switch and it's associate services
investigating
We are currently experiencing a Public network issue in rack DC3 Room 4-6 Rack A08. This is causing a loss of internet traffic for connected dedicated servers.
Network Switch is in an incorrect state, we have asked our local technicians to replace it.
investigating
We are currently experiencing a Public network issue in rack DC3 Room 4-6 Rack A08. This is causing a loss of internet traffic for connected dedicated servers. We are investigating the root cause with our local technicians.
