Scaleway Status

Status impact color legend

Black impact: None
Yellow impact: Minor
Red impact: Major
Blue impact: Maintenance

[DC3] Public switch DOWN - Room 4 4 Rack E12

Investigating - We are currently experiencing a network incident in DC3 due to a switch failure.
This is impacting a subset of Dedibox servers, which may face intermittent or total loss of network connectivity.

Our teams are actively working to restore full service as quickly as possible.
Jul 08, 2025 - 09:00 CEST

[DC5] Public switch DOWN - Room 1 1 Rack A16

Investigating - We are experiencing a temporary issue affecting some dedicated server.

Team has been warned.
Jul 08, 2025 - 07:30 CEST

[Par2] Llama 3.3 and Gemma3 are unstable

Investigating - Since 6th July 2025, 8:45 PM, Gemma 3 is currently experimenting slow response times and Llama 3.3 experienced a few short disruptions
Jul 07, 2025 - 16:00 CEST

[DC2] Public switch DOWN - Room 101 Rack N15

Monitoring - We experienced a temporary issue affecting a limited number of servers at DC2.
This was due to an internal operation in the datacenter.
As a result, some servers may have become unavailable during the incident.

All impacted servers are currently being restored.
A full recovery is in progress.
Jul 07, 2025 - 13:57 CEST

[NL-AMS] High latencies on Object Storage

Monitoring - Between July 3rd 2:00 PM UTC and July 4th 11:00 AM UTC, customers may have experienced high latencies on Object Storage in the NL-AMS region.
This was due to an internal rebuild process.

To limit the impact, operations were slowed down during the event.
The situation has now stabilized and we are currently monitoring the service closely.
Jul 04, 2025 - 11:01 CEST

[GenAPI] - [fr-par-2] - Service instability

Investigating - Since 30th June 2025, 11:30am, we are experiencing periodic instabilities on the Mistral Small 3.1 inference engine.
This may result in short, intermittent service disruptions for affected users. Investigations are ongoing to find and fix the root cause.
Jul 03, 2025 - 10:01 CEST

[WEBHOSTING] Blacklist Microsoft

Investigating - The IP 51.159.208.135 is blacklisted by Microsoft.

We are currently working on it.
Jun 30, 2025 - 15:06 CEST

About This Site

Welcome to the Scaleway Status website. Here, you can view the status of all Scaleway services across all products and availability zones (AZs).
You can check how subscribe, manage your email status updates and how to receive status notifications on Slack here: https://www.scaleway.com/en/docs/account/reference-content/scaleway-status-updates/

Elements - Products Operational

Instances Operational

Elastic Metal Operational

Apple Silicon Operational

Object Storage Operational

Block Storage Operational

Container Registry Operational

Network Operational

Private Network Operational

Public Gateway Operational

Load Balancer Operational

Kubernetes Kapsule Operational

Serverless Functions and Containers Operational

Serverless-Database Operational

Jobs Operational

Databases Operational

Messaging and Queuing Operational

Domains Operational

IoT Hub Operational

Web Hosting Operational

Transactional Email Operational

IAM Operational

Observability Operational

Secret Manager Operational

Environmental Footprint Operational

Developer Tools Operational

Account API Operational

Billing API Operational

Edge service Operational

Elements Console Operational

Website Operational

Elements - AZ Degraded Performance

fr-par-1 Operational

fr-par-2 Degraded Performance

fr-par-3 Operational

nl-ams-1 Operational

nl-ams-2 Operational

nl-ams-3 Operational

pl-waw-1 Operational

pl-waw-2 Operational

pl-waw-3 Operational

Dedibox - Products Degraded Performance

Dedibox Degraded Performance

Hosting Degraded Performance

SAN Operational

Dedirack Operational

Dedibackup Operational

Domains Operational

RPN Operational

Dedibox Console Operational

Dedibox VPS Operational

Dedibox - Datacenters Degraded Performance

DC2 Operational

DC3 Degraded Performance

DC5 Operational

AMS Operational

Miscellaneous Operational

Excellence Operational

BookMyName Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Jul 8, 2025

Unresolved incidents: [DC3] Public switch DOWN - Room 4 4 Rack E12, [DC5] Public switch DOWN - Room 1 1 Rack A16.

Jul 7, 2025

Unresolved incidents: [Par2] Llama 3.3 and Gemma3 are unstable, [DC2] Public switch DOWN - Room 101 Rack N15.

Jul 6, 2025

No incidents reported.

Jul 5, 2025

No incidents reported.

Jul 4, 2025

[Secondary DNS] - Secondary DNS 62.210.16.8/nssec.online.net is down

Resolved - This incident has been resolved.
Jul 4, 15:56 CEST

Investigating - The secondary DNS server 62.210.16.8/nssec.online.net is down. We are working to resolve that issue as quick as possible.
Jun 30, 16:42 CEST

Jul 3, 2025

[REGX] - [AMS] Container Registry Service Disruption

Resolved - This incident has been resolved.
Jul 3, 15:14 CEST

Monitoring - Fix implemented. Monitoring ongoing.
Jul 3, 15:00 CEST

Identified - Issue identified, fix in progress
Jul 3, 14:55 CEST

Update - We are continuing to investigate this issue.
Jul 3, 14:51 CEST

Investigating - Our teams are currently investigating an issue affecting the container registry service in the AMS region.
This issue may prevent users from pulling or pushing container images, impacting the deployment and operation of containerized applications.

We apologize for any inconvenience caused and will provide updates as soon as more information is available.
Jul 3, 14:25 CEST

[DC5]- RPN Switch replacement in DC5 Room 1 - Rack C51

Completed - The scheduled maintenance has been completed.
Jul 3, 10:00 CEST

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 3, 09:00 CEST

Scheduled - Due to an issue on one of the PSU input of the RPN switch in C51, switch is currently attached to only one power feed.
Due to this, we will proceed with a switch replacement has issue is located on the device itself. Sorry for the inconvenience
Jun 30, 13:11 CEST

Jul 2, 2025

[fr-par-2] Degraded performances due to abnormal temperature

Resolved - This incident has been resolved.
Jul 2, 08:48 CEST

Monitoring - We continue to monitor the situation closely for any further issues.
Jul 1, 18:15 CEST

Identified - The error rate is below the nominal threshold; we are continuing to monitor closely.
Jul 1, 16:30 CEST

Investigating - Due to elevated temperatures in France, some of our services are currently experiencing degraded performance. Our teams are actively implementing mitigation measures and closely monitoring the situation to prevent further impact.
Jul 1, 15:35 CEST

[nl-ams-1] degraded performances due to abnormal temperature

Postmortem - Read details
Jul 3, 18:12 CEST

Resolved - This incident has been resolved.
Jul 2, 02:42 CEST

Update - Situation is back to normal, teams are keeping an eye on it . We are closing this incident.
Jul 2, 02:42 CEST

Update - Most of the services are back online. We are working to clear the few remaining side effects
Jul 2, 01:57 CEST

Update - all servers are now up and running, our teams are now working on restoring services with issues
Jul 2, 00:07 CEST

Update - Backend is now fully up and stable, customer services will begin to come back progressively, we are still monitoring temperature to ramp up the load for the cooling with caution.
Jul 1, 22:41 CEST

Update - We are adding more servers back in production, mostly backend for now, once we are confident all services are ready and cooling keeps stable, customers services will start progressively. We thank you for your patience.
Jul 1, 21:49 CEST

Update - We are seeing improvements in temperatures, we will begin to power up a few internal servers and check how the cooling holds the load
Jul 1, 20:46 CEST

Monitoring - Our datacenter provider has informed us that the situation is stabilized, they expect temperature to improve slowly in the coming hours.
We are checking our own sensors for now, once we are confident the cooling is sufficient we will begin to power on stopped services.
Jul 1, 19:22 CEST

Investigating - Our datacenter provider in nl-ams-1 is unable to provide an update regarding the cooling issue in one of our rooms, we cannot yet share an ETA to restore services on our side. We will provide updates as soon as we have them.
Jul 1, 18:35 CEST

Monitoring - We continue to monitor the situation closely for any further issues.
Jul 1, 18:21 CEST

Identified - To prevent further issues, we will preemptively shut down several services in the datacenter. This may result in temporary downtime for your service. We are doing our best to recover the situation as quickly as possible.
Jul 1, 17:42 CEST

Investigating - Due to elevated temperatures in Netherlands, some of our services are currently experiencing degraded performance. Our teams are actively implementing mitigation measures and closely monitoring the situation to prevent further impact.
Jul 1, 16:30 CEST

Jul 1, 2025

[SSDB] - File system full on worker server

Resolved - This incident has been resolved.
Jul 1, 16:51 CEST

Investigating - The file system on a worker server hosting temporal data is full, causing all backups to fail and logs to not be handled properly.
This may result in data loss and potential disruptions in service.
Jun 30, 12:20 CEST

[DEDIBOX] - [DC5] Network RPN switch failure

Resolved - The switch is back online.
Jul 1, 16:39 CEST

Investigating - A network switch in DC5 room 1 rack C62 has experienced a failure. Dedibox servers in this rack have lost their RPN connectivity. Our technical team is actively working to resolve the issue and restore full connectivity.
Jul 1, 16:07 CEST

Jun 30, 2025

[Network] Redundancy Loss PAR1

Resolved - Equipment has been replaced and everything is back online.
Jun 30, 18:21 CEST

Investigating - Network redundancy loss due to an equipment failure.
All services are still running, but some customer may be impacted by a network redundancy loss.
We are currently working on the matter.
Jun 30, 09:35 CEST

[DNS Resolver] - DNS resolver 62.210.16.6 seems down

Resolved - This incident has been resolved.
Jun 30, 16:40 CEST

Investigating - Our team has noted a new downtime and is actively working on a more sustainable solution.
Jun 30, 16:22 CEST

Monitoring - A fix has been implemented and we are monitoring the results.
Jun 30, 15:58 CEST

Investigating - The legacy DNS resolver 62.210.16.6, used on Dedibox installations before the introduction of new IP addresses, is currently experiencing connectivity issues. This may affect the resolution of DNS queries for impacted Dedibox instances.
Jun 30, 15:26 CEST

Jun 29, 2025

No incidents reported.

Jun 28, 2025

No incidents reported.

Jun 27, 2025

[MGDB] - [fr-par] MongoDB deployment failure

Resolved - This incident has been resolved.
Jun 27, 13:25 CEST

Identified - The issue has been identified and our team is now working on a fix.
Jun 26, 15:32 CEST

Investigating - We are currently experiencing issues with MongoDB deployments in the fr-par region, which are ending in error. This may result in delays or failures when attempting to create new MongoDB instances. Our technical team is actively investigating the issue to restore normal service as soon as possible.
Jun 26, 11:14 CEST

[VPCL] - [nl-ams-3] Connectivity Issue

Resolved - This incident has been resolved.
Jun 27, 11:33 CEST

Monitoring - We sincerely apologize for the inconvenience caused during our recent maintenance operation. The issue has been resolved, and all services should now be back to normal. Thank you for your patience and understanding. If you have any further concerns, please don’t hesitate to contact us.
Jun 26, 17:30 CEST

Identified - Our team is currently working to resolve an issue that occurred during a scheduled maintenance operation. Unfortunately, an error was made when the wrong machines were serviced. Rest assured, our engineers are taking all necessary steps to fix this promptly.
Inter-AZ traffic (including InstanceElastic Metal) in VPC is actually OK. Only DHCP and DNS are affected by the incident on NL-AMS-3.
Jun 26, 17:28 CEST

Investigating - There is currently a connectivity issue affecting the Virtual Private Cloud (VPCL) in the Amsterdam region (nl-ams-3). This issue is causing degradation in DHCP services and DNS resolution.

Impact :
Users may experience difficulties in obtaining IP addresses via DHCP.
DNS resolution may be unavailable, affecting the ability to resolve domain names to IP addresses.
This also impacts the connectivity of instances and Elastic Metal.
Jun 26, 16:49 CEST

Jun 26, 2025

[Object Storage] - Checksum error in some client/sdk

Resolved - This incident has been resolved.
Jun 26, 15:06 CEST

Investigating - S3 checksum error in some client/sdk, we alway return the full object checksum even when the request is ranged, causing issue in some high-level wrappers that try to compare the range's checksum with the full object one.

Full integrity of the objects aren't impacted, and all computed checksum are valid.
May 2, 19:00 CEST

[WEBHOSTING] - Blacklist Microsoft

Resolved - This incident has been resolved.
Jun 26, 13:22 CEST

Update - We are continuing to investigate this issue.
Jun 19, 14:23 CEST

Investigating - We are currently investigating this issue.
Jun 13, 15:26 CEST

Monitoring - A fix has been implemented and we are monitoring the results.
Jun 9, 17:10 CEST

Identified - The IP 51.159.208.135 of our Webhosting platform is blacklisted by Microsoft.
We are currently working on it.
May 27, 10:10 CEST

Jun 25, 2025

Issue on DNS resolvers between Scaleway/Dedibox and Linode autoritative servers

Resolved - This incident has been resolved.
Jun 25, 14:11 CEST

Investigating - We have analyzed an issue to access the autoritative DNS of Linode (at least ns1/2/3/4/5.linode.com) to resolve some domain names (FQDN) from our network.

You may use other DNS resolvers to solve this issue in the meantime than the ones provided with Scaleway and Dedibox if you have issue to resolve some FQDN behind Linode DNS autoritative servers (an example with Unbound and a public DNS like Google : 'unbound-control forward_add alpinelinux.org x.x.x.x').

We are not the sole provider to experience such issue, many other DNS public resolvers we have tested are experiencing the same anomalous behavior.
Jun 24, 14:53 CEST

Jun 24, 2025

[Console] Incorrect quota limits shown in console

Resolved - This incident has been resolved.
Jun 24, 13:31 CEST

Monitoring - A fix has been implemented and we are monitoring the results.
Jun 24, 10:42 CEST

Identified - We've identified an issue where the quotas returned are not always accurate, which can cause the console to display an incorrect maximum value. As a result, certain actions might be limited in the console, even though the actual quotas are higher.

Please note that this issue does not affect actions performed via API, CLI, or Terraform. Only the web console is impacted.
Jun 24, 09:38 CEST

Payments Scaleway & Dedibox

Completed - The scheduled maintenance has been completed.
Jun 24, 12:30 CEST

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 24, 12:00 CEST

Scheduled - Maintenance will be carried out to improve reliability.
the impact could be a short unavailabilities to process payments.
Jun 24, 09:07 CEST